docs don't sufficiently explain difference between update and revert
Bug #809484 reported by
xaav
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
xaav said, incorrectly """Bzr up is redundant; bzr revert accomplishes the same task. There is no need to maintain these two commands; it creates inconsistency and confusion about which one to use."""
The docs should explain the difference more clearly (probably in the guide and in help.)
summary: |
- Bzr up is redundant + docs don't sufficiently explain difference between update and revert |
Changed in bzr: | |
status: | Invalid → Confirmed |
importance: | Undecided → Medium |
tags: | added: doc easy |
description: | updated |
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.
I'm not sure about the 'bzr revno --tree' bug, but I think you are confused. revert is *not* the same as update, because revert *intentionally* doesn't change the working tree revision pointer. Specifically so that if you are at rev 10, and want to undo the previous commit, you can "bzr revert -r -9; bzr commit" to create revision 11 like things were at rev 9.