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

Re: .svn directories (no doubt) revisited

From: Ryan Schmidt <subversion-2006d_at_ryandesign.com>
Date: 2006-11-17 02:30:13 CET

On Nov 16, 2006, at 18:02, Tim Hill wrote:

>> Abandoning the .svn folder strategy and instead storing the data
>> in a folder outside the working copy, as you suggest, would break
>> a characteristic of the current layout, which is that any
>> subfolder of a working copy is itself a completely functioning
>> working copy. Not sure how valuable that characteristic is, but I
>> have made use of it a couple times.
>
> Really?

Yes.

> Have you tried this?
>
> svn co http://server/repo/foo -N
> cd foo
> svn co http://server/repo/foo/bar
>
> These commands work, but you actually have a broken working copy.
> You will *not* get the same as:
>
> svn co http://server/repo/foo
>
> What happens is "foo" contains no record of "bar", so you end up
> with a messed-up disjoint working copy.

No, I don't use svn co -N. Yes, using it in the way you've described
will result in weirdness. Don't do it that way. To accomplish what I
think you want, the correct commands are:

svn co http://server/repo/foo -N
up foo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 02:30:54 2006

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