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

Re: svn commit: r21142 - branches/1.4.x/subversion/libsvn_ra_serf

From: Blair Zajac <blair_at_orcaware.com>
Date: 2006-08-21 19:22:50 CEST

Garrett Rooney wrote:
> On 8/21/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:
>> On 8/21/06, Blair Zajac <blair@orcaware.com> wrote:
>> > It appears that the svnmerge.py script wasn't used to do the merge,
>> as the email
>> > isn't showing a property diff on the branches/1.4.x directory.
>> >
>> > I know it's a small merge, but can we either fix the merge
>> information in the
>> > property on branches/1.4.x or revert the merge by hand and then redo
>> the merge
>> > with svnmerge.py?
>> >
>> > This is really more to get in the habit of using svnmerge.py :)
>> I'm sorry, but I'm not going to use svnmerge.py anytime soon.
>> Firstly, I don't have the python bindings installed as I don't have a
>> recent enough SWIG for Subversion's liking. Secondly, there are no
>> instructions in HACKING on how to use it that I can find.

Good point on the HACKING document, we should update that.

Hopefully, by the time 1.5 comes out, we'll use svn's built in merge tracking

To download it

svn cat http://svn.collab.net/repos/svn/trunk/contrib/client-side/svnmerge.py >
chmod a+x svnmerge

You can look here for a one-page intro here on how use it:


In this case, it would be:

svnmerge merge -r 21142
svn commit -F svnmerge-commit-message.txt

and the commit message in svnmerge-commit-message.txt is the commit message you
supplied to r21142.

> FWIW, svnmerge.py doesn't actually use the python bindings, it just
> calls the command line utilities.
>> IMHO, svnmerge.py should cope gracefully when people can't use it.
>> That's a critical requirement for any 'merge tracking' tool even when
>> we roll it out with 1.5: we're not going to be able to force everyone
>> to update their client to use these new features. -- justin
> It does cope reasonably gracefully, the revision will be listed as
> available for merge, and you'll get a conflict if you actually try to
> merge it (no surprise there), and there are commands you can run to
> tell svnmerge.py to simply record the merge in the properties, but not
> actually do the merge (since you've already done it). Something like:
> svnmerge.py merge -rWHATEVERREV --record-only

I was looking for that option. Yes, this would be the easiest fix.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 21 19:24:01 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.