aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2024-02-08 21:26:36 +0200
committerEli Zaretskii2024-02-08 21:26:36 +0200
commitd65499e79083fb764517447d4d40ea3222ea2fa2 (patch)
tree1eda9fbe9dbc84ad601c06250e1faa3d00482375
parent571ec583d644b718ce52f938f111d4aa98192471 (diff)
downloademacs-d65499e79083fb764517447d4d40ea3222ea2fa2.tar.gz
emacs-d65499e79083fb764517447d4d40ea3222ea2fa2.zip
; Another clarification in CONTRIBUTE.
-rw-r--r--CONTRIBUTE7
1 files changed, 4 insertions, 3 deletions
diff --git a/CONTRIBUTE b/CONTRIBUTE
index 049ca00089e..687aa0888ab 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -213,8 +213,9 @@ formatting them:
213 enforced by a commit hook. 213 enforced by a commit hook.
214 214
215- If only a single file is changed, the summary line can be the normal 215- If only a single file is changed, the summary line can be the normal
216 file first line (starting with the asterisk). Then there will be no 216 first line of a ChangeLog entry (starting with the asterisk). Then
217 individual ChangeLog entries beyond the one in the summary line. 217 there will be no individual ChangeLog entries beyond the one in the
218 summary line.
218 219
219- If the commit has more than one author, the commit message should 220- If the commit has more than one author, the commit message should
220 contain separate lines to mention the other authors, like the 221 contain separate lines to mention the other authors, like the
@@ -245,7 +246,7 @@ formatting them:
245- Explaining the rationale for a design choice is best done in comments 246- Explaining the rationale for a design choice is best done in comments
246 in the source code. However, sometimes it is useful to describe just 247 in the source code. However, sometimes it is useful to describe just
247 the rationale for a change; that can be done in the commit message 248 the rationale for a change; that can be done in the commit message
248 between the summary line and the file entries. 249 between the summary line and the following ChangeLog entries.
249 250
250- Emacs follows the GNU coding standards for ChangeLog entries: see 251- Emacs follows the GNU coding standards for ChangeLog entries: see
251 https://www.gnu.org/prep/standards/html_node/Change-Logs.html or run 252 https://www.gnu.org/prep/standards/html_node/Change-Logs.html or run