SVK behaves this way by default,
If you rm -rf a subdirectory svk update will not bring it back.
Instead it shows up as ! (missing). Only a svk revert -R will bring
it back.
I think clkao already mentioned once here that this might be a useful
behavior for svn as well.
Michael
On Sep 22, 2005, at 5:12 PM, Daniel Rall wrote:
> On Thu, 22 Sep 2005, Tim Shadel wrote:
> ...
>
>> So it seems important to have a way to say "I don't want this
>> in my working copy anymore. Please don't bring it back
>> unless I ask for it." Since that can only be done
>> by manipulating the .svn\entries file, it has to be a
>> features of svn, and not simply a combination of
>> operating system features and "svn st".
>>
>
> As you mention in the next paragraph, this can also be handled by
> not checking some sub-directories out in the first place.
>
>
>> I've been using 'svn' since 0.18, so it took me quite
>> a while to figure out why this worked in CVS. It is the
>> interplay between two commands: 'cvs release -d' nukes
>> the directory, and 'cvs update' **unlike svn update**
>> will **NOT** bring down missing directories, so you can
>> remain isolated until you run 'cvs update -dP' which
>> is **much more like svn**. Does that ring any bells?
>> So the old 'cvs release -d' CAN be recreated from
>> operating system commands, but the svn version cannot.
>> Kind of a time warp to recall those details. :-)
>>
>
> How about using a combination of 'svn co -N URI', 'svn ls URI',
> and 'svn co' of desired sub-directories found by 'svn ls'?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 23 05:32:50 2005