On Jun 10, 2005, at 6:05 PM, Max Bowsher wrote:
> Scott Palmer wrote:
>>
>>> Doesn't svn:ignore fulfil this purpose already?
>>>
>>
>> Not really. Since svn:ignore is a property set on the versioned
>> folder it could easily not include things that shouldn't be versioned
>> but aren't cumbersome enough that any specific user cared that they
>> showed up in the status command. Also there is no control of what
>> files someone might put in their WC, so the global (all users) nature
>> of svn:ignore can't possibly know enough for the specific WC that the
>> command is executed on. E.g. users might have little scripts that
>> are specific to their WC.
>>
>
> Then they can sort out some standard naming pattern in order apply
> svn:ignore to them.
> Would they really want to remember to type --exclude foo *every* time?
For all I know that's what is in one of those scripts ;-)
Seriously, I rarely have svn:ignore set up to ignore everything that
it possibly could. I often have experimental files or data files of
some sort in my WC that I don't want to ignore, and I don't want to
add. These are test files that are specific to my working environment.
> If we did decide to go ahead with some kind of --exclude, it would
> make more sense to do it generally, and make it available to
> *every* recursive command, not just this one.
Agreed.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 11 00:38:42 2005