Difference between revisions of "Activity Team/Git Migration"

From Sugar Labs
Jump to navigation Jump to search
Line 25: Line 25:
 
*A [[Activity Team/Git FAQ|Git/Gitorious FAQ]]
 
*A [[Activity Team/Git FAQ|Git/Gitorious FAQ]]
 
*[http://cgit.sugarlabs.org/ cgit] interface for git.sugarlabs.org
 
*[http://cgit.sugarlabs.org/ cgit] interface for git.sugarlabs.org
**http://wiki.sugarlabs.org/go/Activity_Team/Git_Activity_Maintainer_Walkthrough
+
*http://wiki.sugarlabs.org/go/Activity_Team/Git_Activity_Maintainer_Walkthrough
 
[[Category:Activity Team]]
 
[[Category:Activity Team]]

Revision as of 05:40, 3 September 2011

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

How to migrate activity source control from laptop.org to sugarlabs.org.

Import a module from dev.laptop.org

git clone git://dev.laptop.org/projects/pippy-activity
  • 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:pippy-activity/mainline.git 
  • Add the pootle user as a committer (from the "add committer" link on the mainline page) and send mail to Sayamindu, to point pootle to new remote.
  • Notify sugar-devel about the move.
  • Make sure that sugar-jhbuild points to the new repository (ask someone to do it for you if you have no access)

See also