Difference between revisions of "Activity Team/Git Migration"

From Sugar Labs
Jump to navigation Jump to search
m
m
Line 12: Line 12:
 
  git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror
 
  git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror
  
* Give access to the pootle user and send mail to [[User:SayaminduDasgupta|Sayamindu]], to point pootle to new remote.
+
* ''Give'' access to the pootle user and send mail to [[User:SayaminduDasgupta|Sayamindu]], to point pootle to new remote.
* Notify sugar-devel about the move.
+
* ''Notify'' sugar-devel about the move.
  
 
== Clone a module from git.sugarlabs.org ==
 
== Clone a module from git.sugarlabs.org ==

Revision as of 21:57, 15 December 2008

Import a module from dev.laptop.org

  • Get an account on http://git.sugarlabs.org
  • Log in and create a new project from the projects page.
  • Clone your git module from dev.laptop.org
  • See all the remote branches with:
git remote show origin
  • Check out the remote branches you want to migrate, e.g.
git checkout -b sucrose-0.82 origin/sucrose-0.82
  • Push it to git.sugarlabs.org with something like:
git push gitorious@git.sugarlabs.org:sugar/mainline.git --mirror
  • Give access to the pootle user and send mail to Sayamindu, to point pootle to new remote.
  • Notify sugar-devel about the move.

Clone a module from git.sugarlabs.org

Instructions on how to clone a project from the git repositories of sugarlabs.org can be found at the project page, for example for sugar-jhbuild. And here is an example:

git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild