Christopher Ness <chris@nesser.org> wrote:
>> So.... is there a way to create global ignores that are
>> repository-wide?
>
> You can on the client. See:
> http://subversion.tigris.org/faq.html#ignore-commit
I actually saw this, but it's not what I'm looking for.
> You can write a pre-commit script to reject a transaction that contains
> a file to be ignored at the repository gateway. This causes the entire
> commit to fail until the ignored file is removed from the transaction.
> http://svnbook.red-bean.com/en/1.0/ch05s02.html#svn-ch-5-sect-2.1
That could be useful, but doesn't really address the concern since
sometimes I do want to check in files that are in the global ignore
list in CVS.
My goal isn't to prevent the user from committing certain files. My
goal is to prevent svn status from complaining about certain files.
The situation is that our release system currently makes sure that
there are no files in the working copy (CVS sandbox) that are out of
date and won't allow us to release if there are any. (In other words,
cvs -qn update, to be replaced with svn status -u, has to not generate
any output.) Since our build and test systems create certain standard
automatic files, I want to put these in the global ignore instead of
having this information duplicated in a million directories spread
throughout the repository. I can think of workarounds that would more
or less automate the process of managing the svn:ignore property on a
per-directory basis, but it's not really clean. As policy about
global ignores changes over time, things get to be quite messy.
If the feature isn't there, I'll figure out a way around it, but I
want to make sure the feature really isn't there first.
--Jay
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 10 20:46:02 2005