>> 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?
Yes!
But I proposed a new property for the following reason:
Not all files which should be ignored by subversion
are temorary and should be deleted.
For example, suppose a team uses the convention that
all files "private*" per convention are ignored by svn.
For example, a developer may create a local backup copy
"private_myfile.c" from "myfile.c" for some days.
Then the user does not want that his local backup copy
is suddenly deleted by svn.
But you are right:
The advise would be to use always svn:temporary for temporary
files, also if you don't plan to delete them some day.
In addition, svn:temporary indicates that svn may delete
these files, where svn:ignore indicates
that svn does not touch these files.
Cheers,
Folker
---------------------------------------------------------------------
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:17:57 2003