<div class="gmail_quote">2009/1/22 Aaron Bentley <span dir="ltr"><<a href="mailto:aaron@aaronbentley.com">aaron@aaronbentley.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="Ih2E3d"><br>
Marius Kruger wrote:<br>
> For me it is a bit of a nuisance to update other locations like the<br>
> default push/pull locations when binding to or checking out something.<br>
<br>
</div>You shouldn't need push/pull locations with a checkout. Checkouts are<br>
updated with "bzr update", not "bzr pull". You don't push a checkout<br>
because when you commit to a checkout, it's pushed to the bound branch<br>
automatically.<br>
</blockquote></div><br>I know that.<br>But when binding to a new location you might need to do a push first <br>for in case you have extra local revisions. This can cause chaos if you <br>don't push it up and later on do a commit which tells you to do a update with local changes and local commits.<br>
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.<br><br>I still think it would be good to have some nice UI for setting locations.<br>
<br>