Commit message guidelines: Difference between revisions

Commit message guidelines (view source)

1 byte removed , 18 March 2012

m

no edit summary

657

edits

Revision as of 18:45, 17 March 2012 (view source) JordiGH (talk \| contribs) No edit summary ← Older edit		Revision as of 12:34, 18 March 2012 (view source) KaKiLa (talk \| contribs) mNo edit summary Newer edit →
Line 1:		Line 1:
	Our commit messages for Mercurial get ~~automaticallyo~~ distilled into GNU Changelog entries. The GNU coding standards have [http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html some guidelines] for how to write Changelogs, and since Octave is a GNU project, we try to produce Changelogs in this style. However, certain things have to be adapted because the style in there is primarily for C sources, and because we are producing them from Mercurial commit messages.		Our commit messages for Mercurial get automatically distilled into GNU Changelog entries. The GNU coding standards have [http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html some guidelines] for how to write Changelogs, and since Octave is a GNU project, we try to produce Changelogs in this style. However, certain things have to be adapted because the style in there is primarily for C sources, and because we are producing them from Mercurial commit messages.

	You can see how Mercurial will produce the Changelog-style output with the following command:		You can see how Mercurial will produce the Changelog-style output with the following command: