submit_branch automatic handling is confusing

Bug #782169 reported by Vincent Ladeuil on 2011-05-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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


- 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

Vincent Ladeuil (vila) on 2011-05-13
Changed in bzr:
status: New → Confirmed
importance: Undecided → Medium
tags: added: config confusing-ui merge
Vincent Ladeuil (vila) on 2011-05-14
Changed in bzr:
assignee: nobody → Vincent Ladeuil (vila)
Vincent Ladeuil (vila) on 2011-05-26
Changed in bzr:
milestone: none → 2.4b3
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers