summaryrefslogtreecommitdiff
path: root/CONTRIBUTE
diff options
context:
space:
mode:
authorNoam Postavsky <npostavs@gmail.com>2020-09-25 16:10:56 +0200
committerLars Ingebrigtsen <larsi@gnus.org>2020-09-25 16:10:56 +0200
commit499848d8407855d8ca24f0c175c602a0f24da074 (patch)
treee6793909887169d0d494ab8969d1eaf32ee5a770 /CONTRIBUTE
parent307b6f935318b7de23feeba72f66e6fecb0e79d0 (diff)
downloademacs-499848d8407855d8ca24f0c175c602a0f24da074.tar.gz
* CONTRIBUTE: Don't recommend action stamps
* CONTRIBUTE: Remove mention of the "action stamp" thing (bug#20609).
Diffstat (limited to 'CONTRIBUTE')
-rw-r--r--CONTRIBUTE9
1 files changed, 4 insertions, 5 deletions
diff --git a/CONTRIBUTE b/CONTRIBUTE
index 4e42c7aafcc..cb09391c324 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -257,13 +257,12 @@ them right the first time, so here are guidelines for formatting them:
- There is no standard or recommended way to identify revisions in
ChangeLog entries. Using Git SHA1 values limits the usability of
the references to Git, and will become much less useful if Emacs
- switches to a different VCS. So we recommend against that.
+ switches to a different VCS. So we recommend against doing only that.
One way to identify revisions is by quoting their summary line.
- Another is with an action stamp - an RFC3339 date followed by !
- followed by the committer's email - for example,
- "2014-01-16T05:43:35Z!esr@thyrsus.com". Often, "my previous commit"
- will suffice.
+ Prefixing the summary with the commit date can give useful context
+ (use 'git show -s "--pretty=format:%cd \"%s\"" --date=short HASH' to
+ produce that). Often, "my previous commit" will suffice.
- There is no need to mention files such as NEWS and MAINTAINERS, or
to indicate regeneration of files such as 'lib/gnulib.mk', in the