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

Re: Newbie /etc/subversion question

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-04-15 17:02:51 CEST

Weintraub, David wrote:
> This brings up another problem with Subversion: The Admin has little power
> to enforce CM standards. I am basically given a single big stick: I can
> prevent someone from committing a change I don't want. But, there is
> little
> else I am allowed to do.
> For example, if someone does a commit, I'd like to prompt them for a
> defect
> ID. Yes, I know that the TortoiseSVN client can do this, but what if I
> want
> to make sure it is enforced on the server side, and not depend upon a
> particular Subversion client?

And how exactly is the server going to influence the client in this way?

> What if a developer creates a new file, and
> doesn't set the property svn:keyword = "Id" on it? Or, if a file is text,
> make sure it contains a copyright string inside of it?

Then complain, and reject the commit.

> Some of this could be done with an expanded svnadmin command that would
> allow an administrator to do all of the things that svn can do without
> first
> creating a working directory.


> Others would require some way for the server
> to examine the version of the file that is sitting on the client's machine
> without that version of the file being added to the source archive.

Already possible during pre-commit hook. The proposed commit has been placed
in full as a transaction in the repository, and the pre-commit hook can
examine it.
"svnlook cat -t $TXN ..."


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 15 17:09:47 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.