On Nov 16, 2006, at 12:19 PM, Ryan Schmidt wrote:
>
> On Nov 16, 2006, at 07:17, Brad Cox, Ph.D. wrote:
>
>> Hiding these directories in ./.svn breaks lots of thing that I
>> rely on heavily. In vim, I habitually use :e `grep -rl
>> searchString .` to find files containing searchString. But this
>> picks up hits in .svn directories, often lots of them, and if you
>> accidentally change one, it breaks that workarea. Hiding them
>> elsewhere, like ../foldername.svn instead of ./.svn, would avoid
>> this landmine. Yes; I know about | grep -v \.svn/.
>
> 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? 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.
If there was a single .svn folder in a root somewhere, the tool could
check for this because it would always understand that it owned the
entire tree.
--Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 01:03:22 2006