New bug in log -g with 1.5.1

I think the new log -g code in 1.5.1 has added a new bug. In our
1.5.x branch run this command:

svn log -g -c32253

The bug I am seeing is when we create a feature branch, merge it to
trunk. Then later merge trunk to our release branch. When we run log
-g, all starts off well. It shows the merge from trunk, and then
shows that those trunk changes were merges from the feature branch.
Where it then veers into what I think is a bug, is that it then
repeats those changes from the feature branch. It makes it look like
you merged directly from the feature branch to the release branch.

I am attaching a screenshot of how Subclipse shows the above change.
I think it illustrates it better.

-- 
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