submit_branch automatic handling is confusing
Bug #782169 reported by
Vincent Ladeuil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Vincent Ladeuil |
Bug Description
Discussed on the mailing list recently, highlights included:
- merge sets submit_branch by default to a value that it not appropriate for all workflows,
- there is no way to instruct merge to *not* set the option
- that merge is using submit_branch is unclear for many users
Proposals:
- respect --no-remember when the option is not set (i.e. --no-remember always means don't remember, whether or not the option is set)
- create a new option merge_location, merge_branch or bzr.merge.from specific to merge
Related branches
lp:~vila/bzr/782169-remember-better-or-not
- Alexander Belchenko: Approve
-
Diff: 101 lines (+34/-10)4 files modifiedbzrlib/builtins.py (+14/-8)
bzrlib/tests/blackbox/test_merge.py (+14/-0)
doc/en/release-notes/bzr-2.4.txt (+3/-0)
doc/en/user-guide/merging_changes.txt (+3/-2)
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: config confusing-ui merge |
Changed in bzr: | |
assignee: | nobody → Vincent Ladeuil (vila) |
Changed in bzr: | |
milestone: | none → 2.4b3 |
status: | Confirmed → Fix Released |
To post a comment you must log in.