Activity Team/Git Migration - Revision history

Satellit: /* See also */

2011-09-03T11:58:22Z

Satellit: /* See also */

2011-09-03T10:40:49Z

Satellit: /* See also */

2011-09-03T10:40:26Z

Quozl: describe scope of page, remove out of scope procedure

2010-12-29T03:58:41Z

describe scope of page, remove out of scope procedure

← Older revision		Revision as of 23:58, 28 December 2010
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TeamHeader\|Activity Team}}{{TOCright}}</noinclude>		<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 ==

Line 17:		Line 20:
	* '''Notify''' [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] about the move.		* '''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)		* '''Make sure''' that sugar-jhbuild points to the new repository (ask someone to do it for you if you have no access)

	~~== 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's repos/mainline page, for example for [http://git.sugarlabs.org/projects/sugar-jhbuild/repos/mainline sugar-jhbuild]. And here is an example:

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

	== See also ==		== See also ==

Patrol: moved Walter is a wanker 10/Git Migration to Activity Team/Git Migration over redirect: revert

2010-02-24T01:43:35Z

moved Walter is a wanker 10/Git Migration to Activity Team/Git Migration over redirect: revert

← Older revision	Revision as of 21:43, 23 February 2010
(No difference)

Page move vandal: moved Activity Team/Git Migration to Walter is a wanker 10/Git Migration: Walter is a wanker

2010-02-24T00:20:08Z

moved Activity Team/Git Migration to Walter is a wanker 10/Git Migration: Walter is a wanker

← Older revision	Revision as of 20:20, 23 February 2010
(No difference)

Dfarning: move section on commit messages

2009-08-30T18:48:25Z

move section on commit messages

← Older revision		Revision as of 14:48, 30 August 2009
Line 22:		Line 22:

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

	~~== Git commit message guidelines ==~~
	These are guidelines to enhance the readability of the commit messages and the release notes which are made with [http://www.kernel.org/pub/software/scm/git/docs/git-shortlog.html git-shortlog]. Please try to follow them as much as possible and make suggestions in the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar devel mailing list] of you find things missing, the guidelines completely insane or just want to demonstrate your appreciation.

	* The commit message should start with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. Tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit in the body. The git-shortlog command that we use to write the release notes will strip the more detailed description.

	* If your commit does fix a certain bug make sure that the summarizing line contains the bug number prepended by a '#' at the '''end''' of the line (e.g. #14). It is implied that you mean the [http://trac.sugarlabs.org Sugar Labs trac] instance. If not please prepend an identifier like OLPC#123, RH#456, Debian#666, Ubuntu#53.

	* Start your commit message with a capital letter.

	* Suffix no dot at the end of the summarizing line.

	* Fixes for typing errors and pylint fixes happen quite often. Just mark them _Typo and respectively _Pylint for easier reading.

	~~----~~

	== See also ==		== See also ==

FGrose at 03:02, 30 August 2009

2009-08-30T03:02:55Z

← Older revision		Revision as of 23:02, 29 August 2009
Line 28:		Line 28:
	* The commit message should start with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. Tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit in the body. The git-shortlog command that we use to write the release notes will strip the more detailed description.		* The commit message should start with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. Tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit in the body. The git-shortlog command that we use to write the release notes will strip the more detailed description.

	* If your commit does fix a certain bug make sure that the summarizing line contains the bug number prepended by a '#' at the '''end''' of the line (e.g. #14). It is implied that you mean the [http://~~dev~~.sugarlabs.org Sugar Labs trac] instance. If not please prepend an identifier like OLPC#123, RH#456, Debian#666, Ubuntu#53.		* If your commit does fix a certain bug make sure that the summarizing line contains the bug number prepended by a '#' at the '''end''' of the line (e.g. #14). It is implied that you mean the [http://trac.sugarlabs.org Sugar Labs trac] instance. If not please prepend an identifier like OLPC#123, RH#456, Debian#666, Ubuntu#53.

	* Start your commit message with a capital letter.		* Start your commit message with a capital letter.

FGrose at 02:51, 30 August 2009

2009-08-30T02:51:14Z

← Older revision		Revision as of 22:51, 29 August 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TeamHeader\|Activity Team}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TeamHeader\|Activity Team}}{{TOCright}}</noinclude>
	== Import a module from dev.laptop.org ==		== Import a module from dev.laptop.org ==

Dfarning: add top and bottom templates

2009-08-29T21:06:13Z

add top and bottom templates

← Older revision		Revision as of 17:06, 29 August 2009
Line 1:		Line 1:
			<noinclude>{{GoogleTrans-en}}{{TeamHeader\|Activity Team}}</noinclude>
	== Import a module from dev.laptop.org ==		== Import a module from dev.laptop.org ==

Line 42:		Line 43:
	*[http://cgit.sugarlabs.org/ cgit] interface for git.sugarlabs.org		*[http://cgit.sugarlabs.org/ cgit] interface for git.sugarlabs.org

	[[Category:~~Development~~ Team]]		[[Category:Activity Team]]

← Older revision		Revision as of 07:58, 3 September 2011
Line 26:		Line 26:
	*[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
			*http://people.sugarlabs.org/Tgillard/git-from-bottom-up.pdf
	[[Category:Activity Team]]		[[Category:Activity Team]]

← Older revision		Revision as of 06:40, 3 September 2011
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]]

← Older revision		Revision as of 06:40, 3 September 2011
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
	[[Category:Activity Team]]		[[Category:Activity Team]]