8 Apr
2012
8 Apr
'12
9:09 a.m.
On 7 April 2012 22:06, Eric Niebler <eric@boostpro.com> wrote:
I was thinking of something a little more finessed. :-) For instance, if changelist N only touches one file, and I merge that change to that one file (instead of doing it at the root), the results *should* be the same, right? But it sounds like they're not. The mergeinfo forks, in a sense. There should be a way to automatically detect and fix up these sorts of pointless mergeinfo forks.
I don't know why it doesn't do that. It does try to remove child data when you merge a parent directory (or record a merge), but it can only do that if the child merge data is exactly the same as the merge data it inherits from the parent, and I think that our messy history makes that unlikely.