unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Radon Rosborough <radon.neon@gmail.com>
To: yurivkhan@gmail.com
Cc: Eli Zaretskii <eliz@gnu.org>,
	Andy Moreton <andrewjmoreton@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Use of "Action stamps" in commit messages
Date: Fri, 13 Jul 2018 11:30:11 -0600	[thread overview]
Message-ID: <CADB4rJGQg6A=xHFF5hjHUW5wwyL_aq+6W2JqxxUjEOf4ogxR5w@mail.gmail.com> (raw)
In-Reply-To: <CAP_d_8Usnq2q=v8pDWDwJqArjEpNjVO2vm5Aa=RgJMDRAPg3cw@mail.gmail.com>

>> 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.

The tool will know all the valid Git commit IDs, though. It could
translate unambiguous prefixes of more than 12 characters (or
something) automatically, and then prompt the user to resolve the
rest. It seems to me like translating the whole thing wouldn't be more
than an afternoon's work—are there really that many hexadecimal
numbers that happen to be prefixes of Git commit IDs in commit
messages?

IOW, although there are complications, this is something that would
only happen extremely rarely, and would only have to be done by one
person, and probably won't even happen at all. Whereas the alternative
solution requires all the developers to expend extra mental energy.



  reply	other threads:[~2018-07-13 17:30 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
2018-07-13 17:30         ` Radon Rosborough [this message]
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='CADB4rJGQg6A=xHFF5hjHUW5wwyL_aq+6W2JqxxUjEOf4ogxR5w@mail.gmail.com' \
    --to=radon.neon@gmail.com \
    --cc=andrewjmoreton@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yurivkhan@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).