[RFC] should ((checkout and bind) or reconfigure) be able to update other locations too?

[Marius Kruger]

2009/1/22 Aaron Bentley <aaron at aaronbentley.com>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Marius Kruger wrote:
> > For me it is a bit of a nuisance to update other locations like the
> > default push/pull locations when binding to or checking out something.
>
> You shouldn't need push/pull locations with a checkout.  Checkouts are
> updated with "bzr update", not "bzr pull".  You don't push a checkout
> because when you commit to a checkout, it's pushed to the bound branch
> automatically.
>

I know that.
But when binding to a new location you might need to do a push first
for in case you have extra local revisions. This can cause chaos if you
don't push it up and later on do a commit which tells you to do a update
with local changes and local commits.
In my case I suppose I can do also do a push/pull --remember for each branch
when binding, to make sure they are in sync and don't have legacy/dangerous
locations hanging around.

I still think it would be good to have some nice UI for setting locations.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090122/2c19161a/attachment.htm