That would be the best solution without doubt.
Maybe this suggestion should go in the dev. mailinglist.
Best Regards,
Jens
-----Original Message-----
From: Leeuw van der, Tim [mailto:tim.leeuwvander@nl.unisys.com]
Sent: dinsdag 2 november 2004 10:05
To: C. Michael Pilato; BRUGGEMAN Jens (JBRG)
Cc: users@subversion.tigris.org
Subject: RE: Re: SVN Update Misc
Wouldn't it be handy for use in shell-scripts, if the command-line
executable would indicate this in it's return-value?
Something like:
0 - successful update, no conflicts
1 - successful update, but with conflicts
2 - error during update
cheers,
--Tim
-----Original Message-----
From: cmpilato@localhost.localdomain
[mailto:cmpilato@localhost.localdomain]On Behalf Of C. Michael Pilato
Sent: Tuesday, November 02, 2004 9:05 AM
To: BRUGGEMAN Jens (JBRG)
Cc: 'users@subversion.tigris.org'
Subject: Re: SVN Update Misc
"BRUGGEMAN Jens (JBRG)" <Jens.Bruggeman@seco-m.be> writes:
> Hi,
>
> Let's say I want to automate the svn update command so each day before
> I get to office, a batch script does an SVN update and if succeeded a
> rebuild of all libraries. How can I detect from the command 'svn
> update' that there were any conflicts during this update which I need
> to manually resolve? (If so, no rebuilding needs to be done.)
Funny you should ask this at the *same time* I'm adding conflict detection
to stress.pl. Simply grep the output of 'svn update' for lines that look
like: 'C /some/path/here'
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 2 10:18:21 2004