2011-04-17 15:38:18 +08:00
|
|
|
Commit Rules
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
This file describes rules and things to think about when creating GIMP
|
|
|
|
|
commits.
|
|
|
|
|
|
|
|
|
|
* Commit message format template:
|
|
|
|
|
|
|
|
|
|
modulename: Summary on one line
|
|
|
|
|
|
|
|
|
|
Detailed description that may span several paragraphs and
|
|
|
|
|
lines. Like this example description that is more than one
|
2013-01-27 23:52:38 +08:00
|
|
|
line. Focus on explaining _why_ the commit is needed.
|
2011-04-17 15:38:18 +08:00
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
|
|
|
|
Bug XXXXXX - Bug title
|
|
|
|
|
|
|
|
|
|
Detailed description that may span several paragraphs and
|
|
|
|
|
lines. Like this example description that is more than one
|
2013-01-27 23:52:38 +08:00
|
|
|
line. Focus on explaining _why_ the commit is needed.
|
2011-04-17 15:38:18 +08:00
|
|
|
|
|
|
|
|
Look at existing commit messages for examples.
|
|
|
|
|
|
|
|
|
|
* Keep NEWS up to date
|
|
|
|
|
|
|
|
|
|
Whenever you make a change that is worthy of being mentioned in the
|
|
|
|
|
NEWS file, update the NEWS file too. The purpose of this rule is to
|
2018-04-26 02:31:11 +08:00
|
|
|
make it as easy as possible to make a GIMP release.
|
