--overwrite flag isn't properly explained
Bug #45405 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
| Breezy |
Triaged
|
Low
|
Unassigned | ||
Bug Description
bzr push --help says "--overwrite ... Ignore differences between branches and overwrite unconditionally". But (apparently) it doesn't overwrite the files, just the revision history. So perhaps the explanation should be "Ignore differences in revision history between branches" or similar.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| status: | Unconfirmed → Confirmed |
| importance: | Medium → Low |
| tags: | added: help push |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
There is a lot of discussion earlier in the help text about when to use --overwrite:
If branches have diverged, you can use 'bzr push --overwrite' to replace
the other branch completely, discarding its unmerged changes.
If you want to ensure you have the different changes in the other branch,
do a merge (see bzr help merge) from the other branch, and commit that.
After that you will be able to do a push without '--overwrite'.
It is possible that the help text could be cleaned up a little bit more.