'bzr status' confused by plain renames
Bug #111288 reported by
John A Meinel
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
In bzr.dev 2472, bzr-0.16rc2 and bzr-0.15 there is a small bug when you rename a file in a directory without informing bzr. It marks a file as 'removed' without marking the target as 'unknown'.
Steps to reproduce:
bzr init mytest
cd mytest
touch a b
bzr add
bzr commit -m 1
mv a a2
bzr status
This will report 'a' as removed, but not report "a2" as missing.
Related branches
lp:~jameinel/bzr/renamed-file-111288
(Merged)
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| assignee: | nobody → jameinel |
| importance: | Undecided → High |
| status: | Unconfirmed → In Progress |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in bzr: | |
| status: | In Progress → Fix Committed |
| Changed in bzr: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Bubba Siggler (bud3) wrote Re: [Bug 111288] Re: 'bzr status' confused by plain renames | #3 |
To post a comment you must log in.
I've been able to reproduce this, so I'll try to fix it.