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

Re: anticipate conflicts with --dry-run in script

From: Luke Imhoff <luke_at_cray.com>
Date: Mon, 12 Jan 2009 15:56:46 -0600

You might have better access to error codes if you used the SWIG
bindings for perl or python or another scripting library like pysvn
(also for python).

On Mon, 2009-01-12 at 13:51 -0800, Jack Bates wrote:
> I have a couple scripts which run "svn merge" periodically, for example:
> http://code.google.com/p/qubit-toolkit/source/browse/trunk/symfony/cron.daily/drop
> I run "svn merge --dry-run" first, to exit and make no changes to the
> working copy if "svn merge" would introduce conflicts. But I am having
> trouble detecting whether it anticipates conflicts because "svn merge
> --dry-run" exits with status zero whether or not it anticipates
> conflicts.
> How can I get my script to exit if "svn merge --dry-run" anticipates
> conflicts?
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1020281
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-12 22:57:51 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.