Difference between revisions of "Activity Team/Git Migration"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
* See all the remote branches with: | * See all the remote branches with: | ||
git remote show origin | git remote show origin | ||
| − | * Check out | + | * Check out the remote branches you want to migrate, e.g. |
git checkout -b sucrose-0.82 origin/sucrose-0.82 | git checkout -b sucrose-0.82 origin/sucrose-0.82 | ||
| − | |||
| − | |||
* Push it to git.sugarlabs.org with something like: | * Push it to git.sugarlabs.org with something like: | ||
Revision as of 10:29, 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.