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

Bug in svn log -g ?

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 31 Oct 2008 11:16:03 -0400

Ran into this while working on a revision graph feature in Subclipse:

$ svn log -c 33238 http://svn.collab.net/repos/svn
------------------------------------------------------------------------
r33238 | kameshj | 2008-09-22 09:11:02 -0400 (Mon, 22 Sep 2008) | 4 lines

On issue-2897-take2 branch:

Merge r32478 through r33234 from trunk.

So this is a fairly recently created branch that was only recently
merged. IOW, I'd think its history is not "corrupt" like some of
older branches were.

$ svn log -g -c 33238 http://svn.collab.net/repos/svn

Seems like it runs forever. It basically goes crazy reporting nested merges.

We really need to get some kind of option to this command so that it
only reports the "first level" of merges and does not recurse into the
nested merges.

BTW, specifying the path to the branch in the command does not make a
difference.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-31 16:16:19 CET

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