From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Use of "Action stamps" in commit messages
Date: Fri, 13 Jul 2018 18:05:23 +0300 [thread overview]
Message-ID: <83fu0nch1o.fsf@gnu.org> (raw)
In-Reply-To: <vz1d0vr2n93.fsf@gmail.com> (message from Andy Moreton on Fri, 13 Jul 2018 16:01:28 +0100)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Fri, 13 Jul 2018 16:01:28 +0100
>
> >> 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").
Yes, but adding a date makes the reference more precise.
> > They will stop being useful if we ever change our VCS.
>
> That is unlikely for the forseeable future.
Yes, we thought that way, too, in the past. We were wrong.
next prev parent reply other threads:[~2018-07-13 15:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 9:13 Use of "Action stamps" in commit messages (WAS: [Emacs-diffs] master babe0d4: Rearrange definition of zerop in subr.el) Noam Postavsky
2018-07-13 12:01 ` Eli Zaretskii
2018-07-13 12:59 ` Use of "Action stamps" in commit messages Andy Moreton
2018-07-13 13:45 ` Eli Zaretskii
2018-07-13 15:01 ` Andy Moreton
2018-07-13 15:05 ` Eli Zaretskii [this message]
2018-07-13 17:07 ` Radon Rosborough
2018-07-13 17:24 ` Yuri Khan
2018-07-13 17:30 ` Radon Rosborough
2018-07-13 17:38 ` Eli Zaretskii
2018-07-13 17:34 ` Eli Zaretskii
2018-07-13 18:17 ` John Yates
2018-07-13 18:48 ` Eli Zaretskii
2018-07-13 15:25 ` Paul Eggert
2018-07-13 18:15 ` Eric S. Raymond
2018-07-13 18:59 ` Eli Zaretskii
2018-07-13 19:06 ` Eric S. Raymond
2018-07-13 19:30 ` Eli Zaretskii
2018-07-13 20:10 ` Paul Eggert
2018-07-13 20:47 ` Eric S. Raymond
2018-07-14 7:08 ` Eli Zaretskii
2018-07-14 14:38 ` Paul Eggert
2018-07-14 15:48 ` Eli Zaretskii
2018-07-14 9:49 ` Andy Moreton
2018-07-14 2:45 ` Noam Postavsky
2018-07-14 2:51 ` Brett Gilio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fu0nch1o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.