From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Use of "Action stamps" in commit messages Date: Fri, 13 Jul 2018 20:34:45 +0300 Message-ID: <83bmbbca4q.fsf@gnu.org> References: <83pnzrckq7.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1531503213 14820 195.159.176.226 (13 Jul 2018 17:33:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2018 17:33:33 +0000 (UTC) Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org To: Radon Rosborough Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 13 19:33:28 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 1fe1wb-0003ju-JG for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 19:33:25 +0200 Original-Received: from localhost ([::1]:38529 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1yi-0008ML-Le for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 13:35:36 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56071) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1xw-0008H5-J0 for emacs-devel@gnu.org; Fri, 13 Jul 2018 13:34:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fe1xr-0007IR-NR for emacs-devel@gnu.org; Fri, 13 Jul 2018 13:34:48 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52215) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1xr-0007I7-Jk; Fri, 13 Jul 2018 13:34:43 -0400 Original-Received: from [176.228.60.248] (port=4017 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fe1xr-0006dy-1C; Fri, 13 Jul 2018 13:34:43 -0400 In-reply-to: (message from Radon Rosborough on Fri, 13 Jul 2018 11:07:26 -0600) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:227355 Archived-At: > From: Radon Rosborough > Date: Fri, 13 Jul 2018 11:07:26 -0600 > Cc: Andy Moreton , emacs-devel > > > 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? How do you know that a particular string of hex digits is a Git SHA1 of a commit? A human might be able to make that decision, but a program that converts the entire repository will be unable to do that reliably. The low reliability of such conversions in the pats was what caused us to adopt the "action stamp" notation. > Sure, it'd be annoying and possibly fairly difficult, but changing to > a different VCS is a thing that -- even if it does happen, which I > doubt -- will happen extremely rarely. It doesn't matter how rarely this happens, because when it does, you want the entire project history to still be readable and useful.