From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: Use of "Action stamps" in commit messages Date: Fri, 13 Jul 2018 16:01:28 +0100 Message-ID: References: <83pnzrckq7.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1531494033 5783 195.159.176.226 (13 Jul 2018 15:00:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2018 15:00:33 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (windows-nt) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 13 17:00:29 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fdzYZ-0001OU-Tu for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 17:00:28 +0200 Original-Received: from localhost ([::1]:37749 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzag-0005Ew-PP for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 11:02:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41317) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzZl-0005Ed-M7 for emacs-devel@gnu.org; Fri, 13 Jul 2018 11:01:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fdzZh-0001oa-N5 for emacs-devel@gnu.org; Fri, 13 Jul 2018 11:01:41 -0400 Original-Received: from [195.159.176.226] (port=37711 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fdzZh-0001nx-FR for emacs-devel@gnu.org; Fri, 13 Jul 2018 11:01:37 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fdzXW-0000Bc-Fq for emacs-devel@gnu.org; Fri, 13 Jul 2018 16:59:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 26 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:2eLrVtLF08gnclVQuqahoDw5ucc= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:227343 Archived-At: On Fri 13 Jul 2018, Eli Zaretskii wrote: >> From: Andy Moreton >> Date: Fri, 13 Jul 2018 13:59:32 +0100 >> >> The Linux kernel convention is nicer: the (shortened) commit id, >> followed by a space and the commit summary line, e.g. >> >> Fixes: 1222ff5275 ("Don't skip epg-tests even with gpg 2.0 (Bug#23561)") > > We wanted an ID that is not specific to Git, having learned that a > hard way from the period we used bzr revision numbers. Using the summary line of the commit message is still useful to help identify the right changeset (as long as you train popel to stop writing bad commit messages like "fix last commit"). >> This ensures that the format is human readable, is easy to parse for >> scripting, and identifies the right commit even if the shortened commit >> id is not unique. > > They will stop being useful if we ever change our VCS. That is unlikely for the forseeable future. AndyM