[RFC] managing push locations?

[Martin Pool]

On 7/9/07, Robert Collins <robertc at robertcollins.net> wrote:
> On Thu, 2007-07-05 at 15:05 +1000, Robert Collins wrote:
> > I'm really confused now.
> >
> > How do I setup the following:
> > 1) By default all branches in ~/source/bzr/ get pushed to
> > sftp://bazaar.launchpad.net/~lifeless/bzr/
> > 2) Selected other branches get pushed elsewhere.
> >
> > It used to be that I setup a root in locations.conf, and achieved (2) by
> > doing 'bzr push --remember ELSEWHERE', but that appears to be broken
> > with tag supporting branches?!
>
> No comments on this? It seems pretty harsh to teach people that 'bzr
> push --remember' is useful and have it suddenly stop working completely
> when they do bzr upgrade :(.

That does sound confusing and unfortunate, and indeed pretty much
breaks the --remember options in common usage.

As I understand it from the documentation (and maybe someone can tell
me if this is incorrect), the search order is always

 1- match from locations.conf
 2- branch.conf for this branch
 3- global bazaar.conf

The docs don't really explain why you would want to use branch.conf as
far as I can see.  I think the reason is so that it will be seen by
other people accessing that branch?  Does it propagate when you
branch? We could usefully explain what options make sense to set in
there.

Could we just have --remember set locations.conf rather than branch.conf?

I'd like to have say 'set' and 'get' (or 'setopt') commands that will
write into those files...

-- 
Martin