http://bugs.grommit.com/show_bug.cgi?id=418
------- Comment #8 from richlowe at richlowe.net 2008-03-21 19:31 PDT ------- (In reply to comment #7) > It just occurred to me that this looks a lot like (and may be > identical to) the TeamWare Bug of Doom scenario. I don't think it's identical to it. Note that the issue with git-formatted diffs only occurs if the destination file already existed *at the time you did a copy or rename over it*, not (to the best of my knowledge), if a file has ever previously existed by that name. If I understand the Teamware bug correctly, this would be similar, but in a far more limited (and rare) situation, and also carry an easy workaround (remove the file in the way of the destination, *then* rename/copy over it). It also only applies in the case where you want an applicable diff -g from a change where that was done in one changeset (either because it was one changeset, or it was multiple and you recommitted), it doesn't appear to affect any other command. -- 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.
