commit incorrectly reports missing files as modified
Bug #553955 reported by
Alexander Belchenko
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
C:\Temp\6>bzr init .
Created a standalone tree (format: 1.9)
C:\Temp\6>echo > foo.txt
C:\Temp\6>bzr add
adding foo.txt
C:\Temp\6>bzr ci -m1
Committing to: C:/Temp/6/
added foo.txt
Committed revision 1.
C:\Temp\6>del foo.txt
C:\Temp\6>bzr st
removed:
foo.txt
C:\Temp\6>bzr ci -m2
Committing to: C:/Temp/6/
missing foo.txt
modified foo.txt
Committed revision 2.
I don't think removed foo.txt is "modified" as commit says. I think it's actually "removed" as status says. Or maybe I misunderstood something?
Related branches
lp:~jelmer/bzr/commit-missing-reports-modified
- Vincent Ladeuil: Approve
-
Diff: 43 lines (+10/-1)3 files modifiedbzrlib/commit.py (+2/-0)
bzrlib/tests/test_commit.py (+5/-1)
doc/en/release-notes/bzr-2.5.txt (+3/-0)
description: | updated |
tags: | added: ui |
tags: | added: commit |
tags: | added: regression |
summary: |
- bzr 2.1: commit incorrectly reports missing files as modified + commit incorrectly reports missing files as modified |
Changed in bzr: | |
status: | Confirmed → Fix Released |
milestone: | none → 2.5b1 |
To post a comment you must log in.
Looks like a pretty shallow bug in commit, bzr seems to record the deletion anyway:
$ bzr st -r1..2
removed:
foo.txt