bzr lp-propose is undocumented (please add to manpage)
Bug #843801 reported by
Paul Sladen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
| bzr (Ubuntu) |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
Bug Description
After reading various internal Canonical mailing lists, I decided to try to use 'bzr lp-propose'
1. man bzr gives no hint of the option
2. bzr lp-propose --help offers some guidance,
Therefore I tried some obvious guesses like:
bzr lp-propose
bzr lp-propose lp:~sladen/explicit-branch/…
most of which produced variations on:
"bzr: ERROR: Not a branch:"
"bzr: ERROR: Source and target branches must be different."
Ideally the documentation in the manpage would give an idiot-compatible example for numpties like me.
Related branches
lp:~jelmer/bzr/bzr.1-launchpad-commands
- Martin Pool: Approve
-
Diff: 69 lines (+18/-2)2 files modifiedbzrlib/doc_generate/autodoc_man.py (+12/-2)
doc/en/release-notes/bzr-2.6.txt (+6/-0)
Revision history for this message
| Paul Sladen (sladen) wrote | #1 |
| description: | updated |
| summary: |
- bzr lp-propose is undocumented (please add to manpapge) + bzr lp-propose is undocumented (please add to manpage) |
| tags: | added: doc launchpad manpage |
| Changed in bzr: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in bzr: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| milestone: | none → 2.6b1 |
| Changed in bzr: | |
| milestone: | 2.6b1 → none |
| Changed in bzr: | |
| status: | In Progress → Fix Released |
| milestone: | none → 2.6b2 |
| Changed in bzr (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| importance: | High → Medium |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| Changed in bzr (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Addendum for the information of fellow numpties; the following appears to have done something:
bzr commit
bzr push lp:~sladen/somewhere
bzr lp-propose
of which the latter seems to implicitly choose the parent(?)/trunk.
(To me the explicit 'bzr push' seems to defeat the point?)