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

RE: Merge commit log messages

From: Sebastian Good <sebastian_at_palladiumconsulting.com>
Date: 2006-08-03 02:27:33 CEST

Blame does indeed show me the revision number, and the comment for that
revision does tell us what revision numbers were merged (almost always), but
there's no way to automatically go find that. I have to open another
repo-browser, find the branch mentioned and do a blame there. Hey, I'm lazy.
I want to point and click!

-----Original Message-----
From: news [mailto:news@sea.gmane.org] On Behalf Of Gavin Lambert
Sent: Wednesday, August 02, 2006 7:17 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Merge commit log messages

Quoth Sebastian Good:
> We work on a project with many active branches. While we like that
> Subversion makes this easy, we find we are frustrated with the commit
> log messages. For many files on "trunk", the only comments for the last
> six months are like "merged changes from branch xxx (revision 123-456)".
> This does nothing to help a developer who wants to know "who did what to
> this file I'm editing!"

Have you had a look at the Blame function? From that you can see who
most recently changed a given line of code. If that turns out to be a
merge, then you can jump over to the branch (by changing the URL and
revision) and do a Blame over there, if you've got multiple developers
committing to a single branch.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Aug 3 02:27:41 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

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