On Wednesday 06 November 2002 01:05, Peter Davis wrote:
> On Tuesday 05 November 2002 13:36, Rafael Garcia-Suarez wrote:
> > In fact if you want to add all files you have to recurse into
> > subdirs. If you want to do this cleanly you may want to check their
> > names against a possible svn:ignore property set on the first parent
> > dir under version control.
>
> If you consider a parent's svn:ignore when selecting children from
> unversioned subdirectories, then svn:ignore should first be copied from the
> parent and set on each of those subdirectories when they themselves are
> added. If you copy svn:ignore to the subdirectories before descending into
> them, then this shouldn't be an issue at all, since svn will then use
> svn:ignore from that directory, and it won't have to look for a parent.
This would be great for some things, like, say *.class to ignore all compiled
Java classes. But this would not always be desired. For instance, the way I
usually use svn:ignore, I have a directory in the base of my project called
'build' where _all_ my built/temporary files go. All other files in my wc are
checked into the repository.
So I set svn:ignore to 'build' on my project root directory, and I don't want
it to be inherited. Usually. So perhaps an option would be in order?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 7 03:05:35 2002