<div class="gmail_quote">2009/1/24 John Carr <span dir="ltr"><<a href="mailto:john.carr@unrouted.co.uk">john.carr@unrouted.co.uk</a>></span><br>...<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've talked on #bzr about "bzr clone" and someone suggested that<br>
defining groups of branches would be quite useful. I tend to agree.<br>
While not colocated branches, i cant help but feel a defined group of<br>
branches is similar enough that they should be considered interface<br>
wise, even if not implemented just yet. </blockquote></div><br>I've experimented with something like this<br>( bzr+ssh://<a href="http://bazaar.launchpad.net/%7Eamanica/%2Bjunk/bzr-multilocation/">bazaar.launchpad.net/%7Eamanica/%2Bjunk/bzr-multilocation/</a> )<br>
One idea was to do something similar to bzr-bookmarks, but with multiple targets.<br>Then you need new commands to work with them nicely.<br><br>Then I found scmproj which was ideal for my situation in that I have lots of components that make up a project. Once configured I can run commands on all or some of the component branches. (We are working on improving its configuration and suggestions are welcome)<br>
It even sort of solves this co-location problem by managing feature branches safely away from your working tree, in a special repo that gets created per component. So you don't clutter up your megaproject with repo's all over the place.<br>
<br>I'm not sure if this will fit your situation, as it sounds if you are trying to run commands on a set of branches of the same component. Maybe we can figure out how to support that.<br><br>regards<br>marius<br><br>