Activity log for bug #85524

Date Who What changed Old value New value Message
2007-02-16 10:03:03 Matthew Paul Thomas bug added bug
2007-02-16 14:17:35 Aaron Bentley description Bazaar 0.14.0, Ubuntu 6.10 When merging another tree into mine produces a conflict, sometimes I will want to discuss the code I am trying to merge with the person who wrote it, to learn more about what they were trying to achieve. Unfortunately, bzr blame on a file that is currently conflicted shows only the authors of chunks of my tree's version of the file (aka .THIS). It does not show the authors of the conflicting chunks from the .OTHER tree; indeed, it seems to ignore the conflicts altogether. bzr blame uses the old annotate API, so it cannot reflect pending merges or changes since the last commit. Original report: Bazaar 0.14.0, Ubuntu 6.10 When merging another tree into mine produces a conflict, sometimes I will want to discuss the code I am trying to merge with the person who wrote it, to learn more about what they were trying to achieve. Unfortunately, bzr blame on a file that is currently conflicted shows only the authors of chunks of my tree's version of the file (aka .THIS). It does not show the authors of the conflicting chunks from the .OTHER tree; indeed, it seems to ignore the conflicts altogether.
2007-02-16 14:17:35 Aaron Bentley title bzr blame on conflicted file shows .THIS, ignoring conflicts bzr blame reflects last-committed revision, not pending changes
2007-02-16 14:19:18 Aaron Bentley bzr: status Unconfirmed Confirmed
2007-02-16 14:19:18 Aaron Bentley bzr: importance Undecided Low
2007-02-16 14:19:18 Aaron Bentley bzr: statusexplanation Gannotate does do this, and it's a much better annotate tool in general
2009-04-22 12:51:43 Marius Kruger bzr: status Confirmed Fix Released
2009-04-22 12:51:43 Marius Kruger bzr: milestone 1.8