more concise syntax for bzr branch lp:project; bzr push lp:~user/project/newbranch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
James Westby suggested I file a wishlist bug about this, so here goes:
When you clone a project with 'bzr branch lp:projectname', make local modifications, and then want to publish that branch, you currently have to use 'bzr push lp:~yourusername/projectname/yourbranchname'.
When I do this, I feel like I'm repeating myself -- I've already specified my launchpad username with 'bzr launchpad-login', and I already specified the project name when I did 'bzr branch' (and I can see that with bzr info). If I want to publish a public branch of that project, the only bit of new information is the name of my branch.
I therefore suggest that Bazaar's launchpad plugin acquire explicit syntax for this use case: making a public branch of a project. I don't have good syntax in mind -- maybe something like 'bzr push lp:+my/newbranchname'? It kind of feels like it follows Launchpad's convention of using '+' for special names, but there may be other considerations.
tags: | added: launchpad |
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: check-for-breezy |
Perhaps I should mention the example that prompted me to file this bug report. According to James Westby, in the future I'll be able to make branches of Ubuntu packages, and publish bugfixes by doing
bzr branch lp:ubuntu/jaunty/packagename
vi; bzr commit --fixes lp:123456
bzr push lp:~mgedmin/ubuntu/jaunty/packagename/mybranchname
Counting the path elements in the last command I cannot help but remember a Monty Python quote: "Five is right out!"