Difference between revisions of "Activity Team/Git Migration"
Jump to navigation
Jump to search
m (→See also) |
|||
| (36 intermediate revisions by 13 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}{{TOCright}}</noinclude> | ||
| + | |||
| + | How to migrate activity source control from laptop.org to sugarlabs.org. | ||
| + | |||
== Import a module from dev.laptop.org == | == Import a module from dev.laptop.org == | ||
| − | * | + | * '''Create''' an account on http://git.sugarlabs.org |
| − | * Log in and create a new project from the projects page. | + | * '''Log in''' and [http://git.sugarlabs.org/projects/new create a new project] from the projects page (please use '''only lower case''', e.g. sugar, turtleart, sugar-toolkit). |
| − | * Clone your git module from dev.laptop.org | + | * '''Clone''' your git module from dev.laptop.org, e.g. |
| − | * See all the remote branches with: | + | git clone git://dev.laptop.org/projects/pippy-activity |
| + | * '''See''' all the remote branches with: | ||
git remote show origin | git remote show origin | ||
| − | * Check out the remote branches you want to migrate, e.g. | + | * '''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: |
| + | |||
| + | 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 [[User:SayaminduDasgupta|Sayamindu]], to point pootle to new remote. | ||
| + | * '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel 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 == | |
| − | * | + | *A [[Activity Team/Git FAQ|Git/Gitorious FAQ]] |
| − | * | + | *[http://cgit.sugarlabs.org/ cgit] interface for git.sugarlabs.org |
| + | *http://wiki.sugarlabs.org/go/Activity_Team/Git_Activity_Maintainer_Walkthrough | ||
| + | *http://people.sugarlabs.org/Tgillard/git-from-bottom-up.pdf | ||
| + | [[Category:Activity Team]] | ||
Latest revision as of 06:58, 3 September 2011
How to migrate activity source control from laptop.org to sugarlabs.org.
Import a module from dev.laptop.org
- Create an account on http://git.sugarlabs.org
- Log in and create a new project from the projects page (please use only lower case, e.g. sugar, turtleart, sugar-toolkit).
- Clone your git module from dev.laptop.org, e.g.
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)