Activity Team/Git Introduction - Revision history

Quozl: /* Commit message guidelines */

2014-12-10T02:36:30Z

Commit message guidelines

← Older revision		Revision as of 22:36, 9 December 2014
Line 32:		Line 32:
	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] if you find things missing, the guidelines completely insane or just want to demonstrate your appreciation.		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] if 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.		* The commit message should start with a single short line summarizing the change (less than 50 characters), followed by a blank line and then a more thorough description (wrapped to 72 characters per line). This is because 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. Also, 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). Please prepend an identifier indicating the bug tracker, e.g. [http://bugs.sugarlabs.org/ticket/342 SL#342], [http://dev.laptop.org/ticket/9358 OLPC#9358], [https://bugzilla.redhat.com/show_bug.cgi?id=482949 RH#482949], [http://bugs.debian.org/555965 Debian#555965], [https://bugs.launchpad.net/sugar/+bug/480407 Ubuntu#480407].		* 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). Please prepend an identifier indicating the bug tracker, e.g. [http://bugs.sugarlabs.org/ticket/342 SL#342], [http://dev.laptop.org/ticket/9358 OLPC#9358], [https://bugzilla.redhat.com/show_bug.cgi?id=482949 RH#482949], [http://bugs.debian.org/555965 Debian#555965], [https://bugs.launchpad.net/sugar/+bug/480407 Ubuntu#480407].

Sascha silbe: /* Commit message guidelines */ fix typo

2011-05-28T20:23:11Z

Commit message guidelines: fix typo

← Older revision		Revision as of 16:23, 28 May 2011
Line 30:		Line 30:

	== Commit message guidelines ==		== 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.		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] if 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.		* 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.

Sascha silbe: /* Commit message guidelines */ prefix Sugar Labs tickets with SL, add links for example ticket references

2011-04-15T21:10:25Z

Commit message guidelines: prefix Sugar Labs tickets with SL, add links for example ticket references

← Older revision		Revision as of 17:10, 15 April 2011
Line 34:		Line 34:
	* 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://~~trac~~.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). Please prepend an identifier indicating the bug tracker, e.g. [http://bugs.sugarlabs.org/ticket/342 SL#342], [http://dev.laptop.org/ticket/9358 OLPC#9358], [https://bugzilla.redhat.com/show_bug.cgi?id=482949 RH#482949], [http://bugs.debian.org/555965 Debian#555965], [https://bugs.launchpad.net/sugar/+bug/480407 Ubuntu#480407].

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

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

2010-02-24T01:43:35Z

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

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

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

2010-02-24T00:20:08Z

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

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

Dfarning: add commit message section

2009-08-30T18:49:52Z

add commit message section

← Older revision		Revision as of 14:49, 30 August 2009
Line 28:		Line 28:

	Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.		Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.

			== 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.

			----

	[[Category:Activity Team]]		[[Category:Activity Team]]

Dfarning: add formating

2009-08-29T21:17:04Z

add formating

← Older revision		Revision as of 17:17, 29 August 2009
Line 23:		Line 23:
	== Gitorious ==		== Gitorious ==

	Gitorious provides open source infrastructure for hosting open source projects that use Git. The central entity in Gitorious is the project, which contains one or more top-level repositories and any repositories managed by the project's contributors.		'''Gitorious''' provides open source infrastructure for hosting open source projects that use Git. The central entity in Gitorious is the project, which contains one or more top-level repositories and any repositories managed by the project's contributors.

	This allows you, as a project administrator, to keep an eye on what people are working on in their individual clones of your repositories. It also lets you merge or provide feedback on their contributions.		This allows you, as a project administrator, to keep an eye on what people are working on in their individual clones of your repositories. It also lets you merge or provide feedback on their contributions.

	Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.		Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.

	[[Category:Activity Team]]		[[Category:Activity Team]]

Dfarning: add gitorious summary

2009-08-29T21:16:11Z

add gitorious summary

← Older revision		Revision as of 17:16, 29 August 2009
Line 20:		Line 20:

	For more information about version control systems, see [http://en.wikipedia.org/wiki/Revision_control Wikipedia]		For more information about version control systems, see [http://en.wikipedia.org/wiki/Revision_control Wikipedia]

			== Gitorious ==

			Gitorious provides open source infrastructure for hosting open source projects that use Git. The central entity in Gitorious is the project, which contains one or more top-level repositories and any repositories managed by the project's contributors.
			This allows you, as a project administrator, to keep an eye on what people are working on in their individual clones of your repositories. It also lets you merge or provide feedback on their contributions.
			Likewise, as a project contributor, you get a place to host your contributions and provide feedback back into the projects ecosystem and easily collaborate with others on the same project. You get your own personal clone of the project on the site that you can work freely in and a way to package up your changes and notify the other project members about your changes.

	[[Category:Activity Team]]		[[Category:Activity Team]]

Dfarning: add intro

2009-08-29T21:14:04Z

add intro

@@ Line 1: / Line 1: @@
 <noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}</noinclude>
-== Git and Gitorious Introduction ==
+== Git ==
 [[Category:Activity Team]]

Dfarning: create page

2009-08-29T20:32:42Z

create page

New page

<noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}</noinclude>
== Git and Gitorious Introduction ==

[[Category:Activity Team]]