From: Yuri Khan <yurivkhan@gmail.com>
To: Radon Rosborough <radon.neon@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
andrewjmoreton@gmail.com, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Use of "Action stamps" in commit messages
Date: Sat, 14 Jul 2018 00:24:33 +0700 [thread overview]
Message-ID: <CAP_d_8Usnq2q=v8pDWDwJqArjEpNjVO2vm5Aa=RgJMDRAPg3cw@mail.gmail.com> (raw)
In-Reply-To: <CADB4rJFqA=JiLo_eib9K9Vv=iQnXbAc=weu=rimtW8mQ-8hTow@mail.gmail.com>
On Sat, Jul 14, 2018 at 12:09 AM Radon Rosborough <radon.neon@gmail.com> wrote:
>
> > They will stop being useful if we ever change our VCS.
>
> Maybe I'm missing something, but -- if we change to a different VCS,
> we are going to have to rewrite all the history anyway. Why would it
> be difficult to have a filter that goes through and replaces all the
> Git commit IDs with the corresponding ones for the new VCS?
Because it is hard for an automatic tool to tell Git commit IDs from
unrelated hexadecimal numbers.
next prev parent reply other threads:[~2018-07-13 17:24 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
2018-07-13 17:07 ` Radon Rosborough
2018-07-13 17:24 ` Yuri Khan [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP_d_8Usnq2q=v8pDWDwJqArjEpNjVO2vm5Aa=RgJMDRAPg3cw@mail.gmail.com' \
--to=yurivkhan@gmail.com \
--cc=andrewjmoreton@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=radon.neon@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).