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

[Stephen J. Turnbull]

John Arbash Meinel writes:

 > I will say that *for me*, I pretty much never write just "bzr
 > merge".

I think that's just you. :-)

 > In fact, I generally never *think* to run just "bzr merge". In my head
 > it is never "I want to sync using merge", it is always "I want to merge
 > *this* branch".

Yup, syncing[sic - not necessarily mirror!] is something I do a lot.
So yup, I think that's just you. :-)

*When this is what I'm doing*, I find it quite annoying that hg and
git don't remember that location, and I want "$VCS $PULLCMD" to Just
Work.  Often this happens in old (before clone automagically set the
pull locations) infrequently updated (so too tedious to fix the
config) repos.  It's even worse when I have push rights and want push
to work too.  So --remember is a nice feature of bzr, because it
guesses what you want to remember and you don't have to find and parse
the config file.

I'm not so sure that bzr should be guessing, except for the parent
being set at "clone" time, though.  *If* git or hg grew a --remember
option, I'd probably use it quite frequently for a couple months for
repos that never got their defaults set.  I don't think the need to
say it explicitly would bother me, because (except when I do something
like move from a homebrew repo hosting setup to gitolite) I almost
never change default pull/push locations, while I only merge feature
branches once in most cases, so wouldn't want to set that as default
anyway.

If I'm actually merging (rather than "catching up", if you see the
difference), then I'm quite happy with specifying the location (and
surprisingly enough, the differences among bzr, git, and hg with
respect to the appropriate command for merging doesn't bother me
either).

 > The one default setting I use 10 times a day is "push_location". I set
 > up most of my locations to push to the appropriate place on launchpad.
 > So I don't have to re-type the long branch names all the time.

Indeed.  But as a developer less active than some of my colleagues in
any given repo, I find it likely that I'll be pulling from there too.

FWIW, another "but maybe that's just me" story. :-)