2008/12/8 Russel Winder <span dir="ltr"><<a href="mailto:russel.winder@concertant.com">russel.winder@concertant.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Marius,<br>
<br>
Any progress on this?</blockquote><div><br>thanks for the reminder, I forgot about this.<br>I'll put it on my todo list. hopefully I'll get a chance this week.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Currently I am storing a list of URLs in a file called .url and have a<br>
shell alias pushBranch that iterates of the entries in the file and<br>
does a push. It would however, be far better to have a Bazaar feature.<br>
<div><div></div><div class="Wj3C7c"><br>
On Tue, 2008-10-21 at 21:30 +0200, Marius Kruger wrote:<br>
> 2008/10/18 Scott Scriven <<a href="mailto:bzr@toykeeper.net">bzr@toykeeper.net</a>><br>
> ...<br>
><br>
> This bug is related:<br>
><br>
> <a href="https://bugs.launchpad.net/bzr-bookmarks/+bug/254936" target="_blank">https://bugs.launchpad.net/bzr-bookmarks/+bug/254936</a><br>
><br>
> Basically, the bookmarks plugin can work, but only for one<br>
> project at a time. It uses a global namespace for bookmark<br>
> names, instead of per-repository, so the bookmark names end up<br>
> being significantly longer than they would be in git or hg.<br>
><br>
> This is a problem for me too.<br>
> I looked at the code and I think it should be fairly simple to fix, so<br>
> I might do it soon:<br>
><br>
> I'm thinking of adding a option --branch like `bzr whoami`, which will<br>
> cause it to be saved in the branch<br>
> in stead of the global location.<br>
> (Branch specific bookmarks will override global bookmarks with the<br>
> same name)<br>
><br>
><br>
> And for some reason, it doesn't always resolve names without a<br>
> 'bm:' prefix. So, instead of 'hg push foo' it ends up being<br>
> 'bzr<br>
> push bm:myproject-foo'.<br>
><br>
> the problem is that AFAIK unspecified protocols paths are assumed to<br>
> be file://<br>
> I dont think it would be possible/desirable to change this behaviour.<br>
></div></div></blockquote></div><br>