http://bugs.grommit.com/show_bug.cgi?id=397
------- Comment #3 from richlowe at richlowe.net 2007-12-12 15:10 PDT ------- This is because after gathering the outgoing nodes on the current branch, we then walk all changes on the current branch (this should probably change, scaling-wise). Because the merge is not yet committed, it is not a revision on the current branch, and as such doesn't pull the just-merged parent onto that branch. I think that makes the special case easier to implement, either in terms of a walkchangerevs analogue that treats the dirstate/workingctx as existing, or simply within the parenttip calculation. -- Configure bugmail: http://bugs.grommit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
