The question: Is there any way, via some config file, to have the svn
commit and status commands (for that matter all svn commands)
automatically exclude or ignore specific directories and/or files when
invoked?
The reason: something probably common to everyone -- when I build a
project, the build creates compiled files within the project that are
not to be stored in subversion (or likewise, users who use IDE's may
have files created by the IDE which aren't to be stored in subversion).
I want svn to *always* ignore these. While I understand that following
proper policy will avoid accidental commits, with large commits, it
still is a nuisance. In addition, it is almost inevitable that at some
point its going to happen, and especially with lesser experienced
developers and those new to subversion. In addition, automation on top
of subversion generally increases the chances of an accident occurring.
For example, Eclipse will ask at commit time if all files not under
subversion's control should be added -- a simple click yes will push all
that junk plus .project and .classpath files into subversion. Its an
easy mistake to make, and with a large commit, a pain to have to
manually filter through the list of files, checking / unchecking boxes.
It would be *really* cool to have an svn.xml file or something like that
which svn looks at to determine what directories and files it should
operate on. Hopefully, I've just displayed my ignorance of something
subversion already does, and everyone can enlighten me to this feature....
Thoughts?
B
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 16 16:31:56 2005