John Peacock <jpeacock@rowman.com> writes:
> Folker Schamel wrote:
>
> > Today, when having such files, you use svn:ignore
> > to tell subversion to ignore these files.
> > You set this property to the directory(!) containing these files.
> >
>
> But you have to imagine that this directory might, at some point, be
> deleted in order to even consider adding that new property. Wouldn't
> it be better all around to extend svn:ignore so that if a directory is
> scheduled for deletion, and there are unversioned files located in
> that directory which match the svn:ignore regex, then subversion will
> feel free to delete that directory in the WC? Wouldn't that meet your
> needs just as well?
Heavens, no! You put stuff in svn:ignore so your version control
system will *ignore* those things. Destroying something "for you" (as
if that's a benefit) is not only *not* ignoring, but is paying a
special sort of pain-inducing attention to those things.
You gotta keep in mind that while UserA might add this new
'svn:temporary' (completely misnamed, but I'll roll with it) because
the only unversioned things he has in his directory are the stuffs
from his build system, UserB -- who did *not* set that property -- may
have other things that match that pattern that he very much does *not*
want blown away.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 18 18:19:25 2003