[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 499848d: * CONTRIBUTE: Don't recommend action stamps
From: |
Lars Ingebrigtsen |
Subject: |
master 499848d: * CONTRIBUTE: Don't recommend action stamps |
Date: |
Fri, 25 Sep 2020 10:12:12 -0400 (EDT) |
branch: master
commit 499848d8407855d8ca24f0c175c602a0f24da074
Author: Noam Postavsky <npostavs@gmail.com>
Commit: Lars Ingebrigtsen <larsi@gnus.org>
* CONTRIBUTE: Don't recommend action stamps
* CONTRIBUTE: Remove mention of the "action stamp" thing (bug#20609).
---
CONTRIBUTE | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/CONTRIBUTE b/CONTRIBUTE
index 4e42c7a..cb09391 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 499848d: * CONTRIBUTE: Don't recommend action stamps,
Lars Ingebrigtsen <=