; Another clarification in CONTRIBUTE.
This commit is contained in:
@@ -213,8 +213,9 @@ formatting them:
|
|||||||
enforced by a commit hook.
|
enforced by a commit hook.
|
||||||
|
|
||||||
- If only a single file is changed, the summary line can be the normal
|
- If only a single file is changed, the summary line can be the normal
|
||||||
file first line (starting with the asterisk). Then there will be no
|
first line of a ChangeLog entry (starting with the asterisk). Then
|
||||||
individual ChangeLog entries beyond the one in the summary line.
|
there will be no individual ChangeLog entries beyond the one in the
|
||||||
|
summary line.
|
||||||
|
|
||||||
- If the commit has more than one author, the commit message should
|
- If the commit has more than one author, the commit message should
|
||||||
contain separate lines to mention the other authors, like the
|
contain separate lines to mention the other authors, like the
|
||||||
@@ -245,7 +246,7 @@ formatting them:
|
|||||||
- Explaining the rationale for a design choice is best done in comments
|
- Explaining the rationale for a design choice is best done in comments
|
||||||
in the source code. However, sometimes it is useful to describe just
|
in the source code. However, sometimes it is useful to describe just
|
||||||
the rationale for a change; that can be done in the commit message
|
the rationale for a change; that can be done in the commit message
|
||||||
between the summary line and the file entries.
|
between the summary line and the following ChangeLog entries.
|
||||||
|
|
||||||
- Emacs follows the GNU coding standards for ChangeLog entries: see
|
- Emacs follows the GNU coding standards for ChangeLog entries: see
|
||||||
https://www.gnu.org/prep/standards/html_node/Change-Logs.html or run
|
https://www.gnu.org/prep/standards/html_node/Change-Logs.html or run
|
||||||
|
|||||||
Reference in New Issue
Block a user