On Feb 10, 2005, at 11:43 AM, Jay Berkenbilt wrote:
> 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.
svn status -q ignores unknown files. Would that work for you in this
scenario?
stephen
---------------------------------------------------------------------
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:53:37 2005