Yeah, an activity specific variant of these instructions exists at <div><br></div><div><a href="http://sugarlabs.org/go/ActivityTeam/How_to_migrate_from_OLPC">http://sugarlabs.org/go/ActivityTeam/How_to_migrate_from_OLPC</a></div>
<div><br></div><div>I didn't think to look for a branch when migrating it though.</div><div><br></div><div>-Wade<br><br><div class="gmail_quote">On Wed, Jan 21, 2009 at 1:44 PM, Morgan Collett <span dir="ltr"><<a href="mailto:morgan.collett@gmail.com">morgan.collett@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">On Wed, Jan 21, 2009 at 20:35, Wade Brainerd <<a href="mailto:wadetb@gmail.com">wadetb@gmail.com</a>> wrote:<br>
> Yikes, I had no idea bout the branch on <a href="http://dev.laptop.org" target="_blank">dev.laptop.org</a> - it wasn't even<br>
> moved over to <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a> in the migration!<br>
> I'll try and merge the branches after work tonight and release v17.<br>
> -Wade<br>
<br>
</div>For the benefit of those yet to move over,<br>
<a href="http://sugarlabs.org/go/DevelopmentTeam/Git#Import_a_module_from_dev.laptop.org" target="_blank">http://sugarlabs.org/go/DevelopmentTeam/Git#Import_a_module_from_dev.laptop.org</a><br>
says:<br>
<br>
* See all the remote branches with:<br>
<br>
git remote show origin<br>
<br>
* Check out the remote branches you want to migrate, e.g.<br>
<br>
git checkout -b sucrose-0.82 origin/sucrose-0.82<br>
<br>
* Push it to <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a> with something like:<br>
<br>
git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror<br>
<br>
So you need to manually look at, and check out, the branches you want<br>
to migrate over.<br>
<br>
Regards<br>
<font color="#888888">Morgan<br>
</font></blockquote></div><br></div>