[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Requests

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: Mon, 23 Sep 2013 18:13:13 -0400

On Sun, Sep 22, 2013 at 8:30 PM, Gavin Lambert <tsvn_at_mirality.co.nz> wrote:

> On 9/21/2013 2:59 AM, Quoth Ben Fritz:
> > Why is this a pathological case?
> >
> > Every project I work on has multiple components which can be worked on
> > separately. We have supporting documentation, we have GUI definition
> > graphics files, we have the code of course, we have separately
> > compiled libraries that go into the project, etc. There are tons of
> > reasons why we might check out a subfolder.
> Maybe it's a cultural/policy thing then. [...]
> In any case, creating copies of the properties makes them impossible to
> maintain / update, because there is no longer a single definitive
> source. At least with the official new 1.8 recursive lookup the
> original issue can be mitigated without copying -- now we just need to
> be able to convince TSVN to stop copying.

I think there is a misunderstanding on Ben's part. His argument overlooks
that in the case of a sub-folder check-out, the SVN client caches the
inherited properties so that these are available without the need to
constantly contact the repository server.

From the SVN Book, version "1.8 nightly", as of Sep 23, 2013:

> Properties inherited from above the root of the working copy are cached
> in the working copy's administrative database when the working copy is
> initially checked out and then refreshed whenever the working copy is
> updated.

Therefore, I agree, starting with version 1.8, there is no longer a need to
copy to a folder's descendents *except* to override inherited values.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-09-24 00:13:20 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.