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

RE: bundle commit messages at merge

From: <adam.cabler_at_mathstar.com>
Date: 2007-07-03 23:32:09 CEST

Thanks. I checked this out at one point, but had a few problems with
it. One things I forgot to mention was that I was hoping for something
server-side since most of us are on windows and using tortoise atm.

-----Original Message-----
From: deckrider [mailto:deckrider@gmail.com]
Sent: Tuesday, July 03, 2007 2:29 PM
To: Cabler, Adam
Cc: users@subversion.tigris.org
Subject: Re: bundle commit messages at merge

We use svnmerg.py which does this, as well as makes other parts of the
merge easier.

It can be found in the contrib section of the subversion source code
package. Some helpful documentation is here:


On 7/3/07, adam.cabler@mathstar.com <adam.cabler@mathstar.com> wrote:
> Hello,
> I've been looking for a while for a way to bundle commit messages
from a
> branch to trunk at merge, but I haven't been able to find a solution.
I was
> wondering if anyone has been able to solve this with a script, or if
> is a fundamental issue that makes this hard ( ie. related to merge
> tracking). To be clear, what I want is to have the option, at merge,
> copy all the commit messages in the merge range to trunk. The reason
> this is that all of the developers in my group work on branches and
> details about commits there. But when merging, none of us take the
time to
> go back and transcribe all of these messages by hand. This makes it
> impossible to tell what happened on trunk by looking at the messages
> Anyway, I would appreciate it if anyone has pointers for information
> how to do this.
> Thanks,
> adam

ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
    Information:  http://www.expita.com/nomime.html
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 3 23:32:31 2007

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.