From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Radon Rosborough Newsgroups: gmane.emacs.devel Subject: Re: Use of "Action stamps" in commit messages Date: Fri, 13 Jul 2018 11:07:26 -0600 Message-ID: References: <83pnzrckq7.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1531501624 24453 195.159.176.226 (13 Jul 2018 17:07:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2018 17:07:04 +0000 (UTC) Cc: Andy Moreton , emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 13 19:06:59 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 1fe1X1-0006F6-9V for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 19:06:59 +0200 Original-Received: from localhost ([::1]:38462 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1Z8-0000k7-9W for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 13:09:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1Y6-0000Zd-3F for emacs-devel@gnu.org; Fri, 13 Jul 2018 13:08:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fe1Y5-0006r8-8S for emacs-devel@gnu.org; Fri, 13 Jul 2018 13:08:06 -0400 Original-Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]:44932) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fe1Y3-0006nx-SA; Fri, 13 Jul 2018 13:08:04 -0400 Original-Received: by mail-lj1-x235.google.com with SMTP id q127-v6so24440677ljq.11; Fri, 13 Jul 2018 10:08:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M+Hw/IWIhXiE6WNKIA5A3LImLGI4NOXqllgR+LfmiJ0=; b=CiRZeqkjr1HzGoqSF+sgfBKaze7Dl74gTmm/DOWZUUiIqUeNmykmcUdv5g9QuSOGQg 84CrDsXnFrNhLGPMfa7WdB6AsHNypjUD2R4Tp6pUnB9EkFJFXHZ+CWlGhqZk/Lu2QKHs +TOthvougd8L1zx3ETuB79PdBfL0pbyW6SLCXR1fWsY6/r5sMTrh7ctWetgt7IenQlIT dTnIYRgnM4/UbBriyDI02exeDthxnrbBBZz7K6RUzY9MM12WuA0kRLVb+VFoXD1x4v+5 u+peS4Xnovs0iOOgFFXTvnkZK69LQRVFovtEL/SU2o9B4S3yESUMquPWRcYegrxFjLTz Ad+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M+Hw/IWIhXiE6WNKIA5A3LImLGI4NOXqllgR+LfmiJ0=; b=UuygMrfZAii7H1gnm4hWdPAn3MTsR+uMPZVrkRC8sCuFIKPU8nFf+4EKQQtmFjpugZ bCchY9+J/Ja13mCBZgxNwYDUeVg5JJRF6l6j/19Ca7ToCdSo23LiBwgzCsLZJKrk0SD7 u3zyaErCJ9d0A6CgzUzjzJeN4265LhvzSk81DdWw8fmyTTewfBa0Hp1liN+jDq6MzN4o KnjR2DZ+bxMPOXLMGUFUNnig4EYaSQBlGVFwJzZykI1iN5q1bTbMGPfWh/uu2ekcf57a 6AWtmFJKonZ6NUkS5du1cOyVwYQ1mmnLgVBxxbZVUzkrqjqGvrgP5l7QHHHL57edlC6N H9IQ== X-Gm-Message-State: AOUpUlGTGJojVcdmizuImT2i6rEjZj9p4ixk2TL5HMu8KUxglBpyYRmD R8etN1zikAuG5MZGnNK4dq5YlXdd8n4KyzDp4ND4zT3H X-Google-Smtp-Source: AAOMgpfTmLIbvIFEK5ENwiTR6nUGJMFFwgX6zveU15sJKwYyDjHRKVwG9PSjCO7a5TLFWLbHs84nw2FiWmX6Vqgn02I= X-Received: by 2002:a2e:3c1a:: with SMTP id j26-v6mr3936878lja.149.1531501682558; Fri, 13 Jul 2018 10:08:02 -0700 (PDT) In-Reply-To: <83pnzrckq7.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::235 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:227352 Archived-At: > 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? 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. I can understand if we avoid using Git commit IDs in the code, where we don't want to rewrite history at all, but why not in the commit messages?