Possible bugs in log -g
From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 18 Feb 2008 14:11:41 -0500
This is with trunk code as of r29411
Tests are using merge tracking sample repository.
Dump here:
http://merge-tracking.open.collab.net/files/documents/147/409/mergetracking.dump
Description here:
I have the entire repository (17 revisions) checked out to make
1) You only seem to ever get one set of merged revisions. For
svn log -g trunk
The r17 revision triggers a lot of merge results (lots of which is
2) Too much mergeinfo. Incorrect filtering?
svn log -g -r17 trunk
This should really just show r16, but winds up showing a ton more.
3) Incorrect mergeinfo
svn log -g branches/b
r12 is a merge from branches/a It should expand to show r11 and does,
$ svn pg -r10 svn:mergeinfo branches/b
NOTE: Merge itself handles this correctly. r7 was a blocked revision
There are other examples of problems, but I would guess that they are
-- 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.orgReceived on 2008-02-18 20:11:53 CET |
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.