"bzr commit" should guide users towards "bzr unbind" when needed
Bug #680134 reported by
Paul Sladen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
If the local repo/tree/
In this case "bzr unbind" makes things "just work".
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
| summary: |
- "bzr commit" should guide users towards "bzr unhind" when needed + "bzr commit" should guide users towards "bzr unbind" when needed |
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: bound-branch |
| tags: | added: check-for-breezy |
To post a comment you must log in.
We should definitely give a better error message in case "bzr commit" is used in a checkout where the user doesn't have write access to the master. The current one depends on the underlying transport and leaks internals.
I think it makes sense to mention "bzr unbind" but it's not necessarily the right command to use. It would be relevant if the user didn't really want a checkout but rather a clone of the remote branch.
Another possibility is that they want to commit to the writable version of the remote branch, e.g. by switching from a http:// URL to a bzr+ssh:// URL. Or perhaps they just want to do a local commit for the moment (--local).