On 2006-01-06 10:36:51 +1100, Chris Holland wrote:
>> So what I'd like is an opposite to the svn:ignore property or something
>> like that which specifies only the patterns to version control instead
>> the patterns not to version control.
>> Another way to handle this may be to make the ignore property handle
>> expressions like *^(cat|dog) , which would ignore anything except cat
>> dog files.
>> If there is already a way to do this that I've missed please let me
> "svn ps svn:ignore '*' ."
> and you only run svn add on file you want to add.
Thanks Marcus. Actually that's what we have been doing for now. The
trouble is that people forget to commit files because when they do an svn
commit, it doesn't show any new files. And if we don't have the ignore,
they see too many files and sometimes miss the ones that we want to version
control. I understand that this is not a problem in most uses of svn, it's
pretty specific to the way we're using it and we want to make it as error
proof as possible.
I've managed a better workaround - say for instance you want to only
version control .cat and .dog files we create an ignore list like this:
Unfortunately this means it will still include files like .cog and .dat, so
you have to then add additional ignores for these if they are common
extensions. If you have five or six file extensions, the number of
combinations becomes very large and the ignore list is very difficult to
read and maintain - and probably time expensive for svn to process as well.
If anyone else thinks this could be valuable, perhaps it could be
considered for a future version.
It would also be nice to be able to have different ignore rules for files
and directories - perhaps putting a slash on the end could denote a pattern
to match a directory - actually I haven't tested this but I guess it won't
If this is the wrong place for "wishlist" items, please point me in the
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jan 9 13:52:53 2006