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

Re: detecting move and copy

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: 2005-07-20 05:36:12 CEST

I never thought about the svn log -v option. Thats something we might
be able to use I think

Thanks much!

SpikeSource Inc.

On 7/19/05, David Weintraub <qazwart@gmail.com> wrote:
> I did some experimenting, and didn't get very far. If I do a "svn log
> -v", I get information that this was a copy. However, you can only use
> "svn log -v" on revisions and not transactions. The "svnlook log"
> command doesn't take a "-v" option. In fact, I couldn't find any of
> the "svnlook" commands that would give me the information (and you
> would need to do an "svnlook" to be able to stop the commit).
> The best you can do is a post-commit trigger that looks at the "svn
> log -v" command output to see if this was in fact a copy and not a
> mkdir. If it was a "mkdir", you could send out an email to yourself,
> so you could have a log talk with the culprit. You could then move the
> offending branch to another directory and clean up the mess.
> It won't prevent someone from making a branch they're not suppose to,
> but it will alert you when it does happen and allow you to fix the
> problem and let the person who did this know they've done you wrong.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 20 23:06:27 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.