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

RE: Pre-commit Hook

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Wed, 30 Jan 2008 12:18:20 -0600

> From: ignacio.lopez_at_tektronix.com [mailto:ignacio.lopez_at_tektronix.com]
> Sent: Wednesday, January 30, 2008 11:55 AM
> To: users_at_subversion.tigris.org
> Subject: Pre-commit Hook

> I'm trying to write a pre-commit hook that prevents the user from
> committing if the files in the transaction if they are not locked
> (this is to force the users to lock the files before editing and
> to make sure no one else is editing the file because most of our
> files are binaries). So far I've been able to run the "svnlook
> lock [repository] [file path in the repository]" command only in
> the command line, the problem is that the pre-commit hook has
> only two parameters Repository and Transaction. Is there a way to
> get a list of all the files included in a transaction? (I am
> running svn on Windows)
 

Use the 'svnlook' commands to see what files are in the transaction. (Specifically 'svnlook changed')
        http://svnbook.red-bean.com/en/1.4/index.html

Search on 'svnlook subcommands' to find the relevant sections.

*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA623

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-30 19:19:20 CET

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.