On Tue, Mar 22, 2011 at 2:34 PM, Cecil Westerhof <ce...@decebal.nl> wrote: > I am executing: > svn propedit svn:ignore . > > But this works only on the current directory. I like to have it work > on all the directories beneath the current directory also. And if > possible on the directories that will be created in the future.
Each and every directory in Subversion can be thought of its own module, so there's no real way for Subversion to know that foo/bar/barfoo is a directory in module /foo/bar, or a another separate module module. That means there's no way for Subversion to know how to handle properties that can affect an entire directory tree. Plus, it would be difficult to know exactly what parent directory is affecting a child directory. For yourself, you can setup a global-ignores that resides in the $HOME/.subversion/config file. That will apply to all working directories in all repositories, but only to you on that particular system (unless your $HOME directory is auto-mounted). Remember that ignoring won't prevent it from being added to the repository. It just makes it harder to accidentally add it to the repository. There are two work arounds: 1). Create a trigger that requires a svn:ignore property on any new directories. You don't put it on, it won't commit the file. 2). You can also have a trigger that bans certain file names. For example, I ban having a directory name "target" in our repository. This prevents users from adding Maven built artifacts to our repository. -- David Weintraub qazw...@gmail.com
