From users-return-28067-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Fri Jun 7 22:37:49 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id CB23B18067E for ; Sat, 8 Jun 2019 00:37:48 +0200 (CEST) Received: (qmail 71220 invoked by uid 500); 7 Jun 2019 22:37:39 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 71210 invoked by uid 99); 7 Jun 2019 22:37:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2019 22:37:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 01519C02CF for ; Fri, 7 Jun 2019 22:37:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.802 X-Spam-Level: * X-Spam-Status: No, score=1.802 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 5FQOrUInkGR8 for ; Fri, 7 Jun 2019 22:37:37 +0000 (UTC) Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id CACF45F419 for ; Fri, 7 Jun 2019 22:37:36 +0000 (UTC) Received: by mail-qt1-f178.google.com with SMTP id s15so4133206qtk.9 for ; Fri, 07 Jun 2019 15:37:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1WzxJJ490ldB2S83Cqp4mU1cnXDIInnN44IQ52gWAt0=; b=DVliNw9IpNP6nzS6rPHWVMiiwF4EXB0jzhq4cfMiB7KlcQIWnNBIufbVWsNdjAjskZ Ad8dbYlKZ+SVbXc6jK7RuvAHNCCjgOBy+CSq0L8tGKGftyr+ThQ7pVFVWHhWvJ1I9Jid tvsPaO59JQsS9RFeOoA67jzdtOjXZo3MsCd2mnQoSfS7g6sM0opt7HDy8uqwmjd4ANkg wu/44FEulLQ8/k1mnTyyKT1rNprzrkGoE8id6WXmb1EKuHArbLfVZfOka04SfjGgHUVB iZvt+e60xmKwvsZv7/FeqwzWAz/oWtu+fGNLsunsLu8RKPlYC+MYGhfgp2QU/E+rBIoq MWqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1WzxJJ490ldB2S83Cqp4mU1cnXDIInnN44IQ52gWAt0=; b=gYMqn0u7sDU5H6dTJsWSfaddFfJcMpptp1HB4ViALxZp3myNV4F7PSLA9KLFfKWpPV lPyILO5jnhF8D6hyOTh9aN15xhtiRjpf1pyKLA7iHs1Ep+dtQnxg0jTURIlNsfSKH5ur I20T8SUO7kBJ0cXVJT8vjBzPm9vKLYx6t/8nO5AXF4wzkyUEv2019YO6/zWdON1akYNJ cQtkeBEYtgrd8FBJ9cVfS/fu0kIlLG2JvOsrz6NF4yI3WTelxs+vE7W7+pX1s4w2TKFe Jm1cghhNLSmfo8eEXTlqUW3J5Bg41maT9/LfiYD7zZ4XtCgFsL2vcNkPc4Ew58zY7pZF bNHQ== X-Gm-Message-State: APjAAAWBYPGYsDKKEJfWl/TCvlX6NUDP7/RjrTzjh08hyuojImEZKpA+ oGIHPo2IDS/z+N0G95nr4Y8tfrACjmg= X-Google-Smtp-Source: APXvYqwkvQt4/Bk5oMMPvGYxSFd5WwLNjp3GP53OHvOyds1wm3XTzKtKLqDY4pvLBzobIrtdnYfyCg== X-Received: by 2002:ac8:3078:: with SMTP id g53mr47061562qte.126.1559947049568; Fri, 07 Jun 2019 15:37:29 -0700 (PDT) Received: from [192.168.5.58] (196-182.spoffordnh.ArgentCom.net. [199.204.196.182]) by smtp.gmail.com with ESMTPSA id s23sm1133366qtk.31.2019.06.07.15.37.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jun 2019 15:37:28 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-E82D006A-9C35-4B54-B2ED-489B8E0A78D8 Mime-Version: 1.0 (1.0) Subject: Re: How to update a sparse directory? From: Mark Phippard X-Mailer: iPad Mail (16G5038d) In-Reply-To: <20190607203419.GB5581@kazan-networks.com> Date: Fri, 7 Jun 2019 18:37:27 -0400 Cc: Subversion Users Content-Transfer-Encoding: 7bit Message-Id: References: <20190607203419.GB5581@kazan-networks.com> To: Mun Johl --Apple-Mail-E82D006A-9C35-4B54-B2ED-489B8E0A78D8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Jun 7, 2019, at 4:34 PM, Mun Johl wrote: >=20 > We're using SVN version 1.8.19 on Red Hat Enterprise Linux 6.8 . >=20 > For one of our projects, the SVN area is a sparse directory. I'm > wondering what's the best way to update that directory? >=20 > I've searched the web but haven't found a definitive answer to how to > _update_ a sparse directory. >=20 > Should I do an "svn update" at the root directory, and then traverse the > lower levels and do updates as well? >=20 > Based on a web answer, I thought "svn update *" at the root level would > work; but it turns out that it doesn't actually update all directories > (at least, not in my case). You just run svn up and it basically says as much in the docs: http://svnbook.red-bean.com/en/1.7/svn.advanced.sparsedirs.html "Fortunately, having a complex collection of ambient depths in a single work= ing copy doesn't complicate the way you interact with that working copy. You= can still make, revert, display, and commit local modifications in your wor= king copy without providing any new options (including --depth and --set-dep= th) to the relevant subcommands. Even svn update works as it does elsewhere w= hen no specific depth is provided=E2=80=94it updates the working copy target= s that are present while honoring their sticky depths." If this is not working for you provide a script that shows what you are doin= g and what you are getting. Mark= --Apple-Mail-E82D006A-9C35-4B54-B2ED-489B8E0A78D8 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Jun 7, 2019, at 4:34 PM= , Mun Johl <mun.johl@kazan= -networks.com> wrote:

We're using SVN version 1.8.19 on Red Hat Enterprise Linux 6.= 8 .

For one of our projects, the SVN area i= s a sparse directory.  I'm
wondering what's the best wa= y to update that directory?

I've searched t= he web but haven't found a definitive answer to how to
_upda= te_ a sparse directory.

Should I do an "svn= update" at the root directory, and then traverse the
lower l= evels and do updates as well?

Based on a we= b answer, I thought "svn update *" at the root level would
w= ork; but it turns out that it doesn't actually update all directories=
(at least, not in my case).

=
You just run svn up and it basically says as much in the docs:


=
If this is not working for you provide a script that shows what you are= doing and what you are getting.

Mark
= --Apple-Mail-E82D006A-9C35-4B54-B2ED-489B8E0A78D8--