bzr merge should allow user to ignore changes in deleted files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Consider following scenario:
* two branches a and b (b was branched off of a, some time in the past)
* new changes on branch a add file x, which is not needed on branch b
* we try merge from a to b
* in order to get rid of x, we run 'bzr revert x' in b
* 'bzr commit' in b
* some time later, changes are done to x on branch a
* upon running merge from a to b, we'll get a conflict with file x - it is removed in b, yet there are changes in it to be merged.
Perhaps it would be useful to add a --ignore-
tags: | added: wishlist |
tags: |
added: conflicts merge removed: wishlist |
Changed in bzr: | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
tags: | added: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
tags: | removed: check-for-breezy |
The conflict should occur only once, subsequent merges should just respect the local decision to delete the file.
Are you experiencing repeated conflicts ?