annotate should include the working tree in the files being annotated
Bug #3439 reported by
Robert Collins
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Wishlist
|
Robert Collins | ||
Bug Description
When I run 'annotate foo' and I have edited foo, I expect to see the version of foo in front ot me. I would expect to have to use 'annotate -r -1' to see the basis copy, or -r X to annotate an arbitrary revision.
Related branches
lp:~lifeless/bzr/3439
(Merged)
Revision history for this message
| Michael Ellerman (michael-ellerman) wrote | #1 |
| Changed in bzr: | |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
Revision history for this message
| Martin Pool (mbp) wrote | #3 |
Revision history for this message
| Martin Pool (mbp) wrote | #4 |
Revision history for this message
| Martin Pool (mbp) wrote | #5 |
| Changed in bzr: | |
| assignee: | nobody → lifeless |
| Changed in bzr: | |
| milestone: | none → 1.8 |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
As I see it annotate is about looking at history, not working changes, but that could be just because that's the way annotate has always worked. I think we'd have to discuss this one on the list.
From a brief look at the code this won't be that easy, the annotation is tied directly to the weave, and AIUI we don't have a weave until we commit, so we'd have to fudge one up for the working tree?