[RFC] I want to disable submit_branch on my computer for all branches. How can I do that?

Stephen J. Turnbull stephen at xemacs.org
Sun May 15 13:40:43 UTC 2011


vila writes:
 > >>>>> Stephen J Turnbull <stephen at xemacs.org> writes:
 > 
 >     > vila writes:
 >     >> >>>>> Stephen J Turnbull <stephen at xemacs.org> writes:
 >     >> 
 >     >> > vila writes:
 >     >> >> The point here is that --remember as it is implemented is not
 >     >> >> related to the fact that the setting is remembered if it doesn't
 >     >> >> exist.
 >     >> 
 >     >> > Then the complaint is about the officious behavior of "bzr
 >     >> > merge" when submit_branch is unset.  My advice it to just
 >     >> > make it stop doing that, and ask the user to always use
 >     >> > --remember.
 >     >> 
 >     >> Right, that's what I've been saying since my first mail, is my English
 >     >> *that* bad ?
 > 
 >     > No, and no.  In the recent mails, you quite clearly, in more than
 >     > adequate English, recommend using --no-remember to reset submit_branch
 >     > to None,
 > 
 > No. I always talked about using --no-remember to inhibit remembering the
 > location at the *first* use (or more precisely when no location have
 > been remembered).

OK, I guess I misunderstood that.

 >     > and make that sticky so that merge won't set it in the future
 >     > (unless the user explicitly specifies --remember).
 > 
 > Neither.

That definitely is sucky interface.  That means that users who don't
want submit_branch set behind their backs must always use
--no-remember (to prevent bzr from misbehaving).

I don't really care though, because my usage patterns never run into
this particular mischief.





More information about the bazaar mailing list