[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "System-wide configuration area" and global-ignores

From: Matt England <mengland_at_mengland.net>
Date: 2005-11-16 17:52:33 CET

At 11/16/2005 09:49 AM, Matt England wrote:
>>If you want to prevent anyone from committing, for example, *.o files
>>to the repository, you can write a pre-commit hook that gets a list
>>of all files in the transaction, does pattern matching on them to see
>>if any prohibited files are listed, and if so, outputs a message to
>>that effect and exits with a nonzero code, which cancels the commit.
>>The user then corrects the problem and attempts the commit again.
>I suppose this is the only server-side "master" control to do what I seek?

If it is, I'm wondering how the default global-ignores value is implemented.

Is it:

1) hard-coded into the source code
2) in some server-system-wide config file
3) something else?

If #2, then where is this config file? I want to change it to include some
more files.

If it's in #1, then I may be interested in changing said source file(s) and
rebuilding the server software to change the default global-ingores value
so that I don't have to hack away at a pre-commit repo hook for every

Whatever the case may be, it seems clear to me that Subversion could
benefit from a server-wide and a repo-specific property control mechanism
(without hard-coding/recompiling) to satisfy this stuff...*without* having
to resort to client-configure-control nightmares.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 16 17:54:57 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.