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:30:11 -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" Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1531502967 28912 195.159.176.226 (13 Jul 2018 17:29:27 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2018 17:29:27 +0000 (UTC) Cc: Eli Zaretskii , Andy Moreton , emacs-devel To: yurivkhan@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 13 19:29:23 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 1fe1sg-0007MB-4b for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 19:29:22 +0200 Original-Received: from localhost ([::1]:38521 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1ul-0007Cm-K8 for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 13:31:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54830) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fe1u6-0007CS-Ll for emacs-devel@gnu.org; Fri, 13 Jul 2018 13:30:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fe1u5-00044A-PD for emacs-devel@gnu.org; Fri, 13 Jul 2018 13:30:50 -0400 Original-Received: from mail-lf0-x231.google.com ([2a00:1450:4010:c07::231]:39554) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fe1u4-0003zu-EG; Fri, 13 Jul 2018 13:30:48 -0400 Original-Received: by mail-lf0-x231.google.com with SMTP id a134-v6so27792640lfe.6; Fri, 13 Jul 2018 10:30:48 -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:content-transfer-encoding; bh=JRDtfxa/q7/WfPcObl3GZoIQHK9I7lvS+uSXR8x1UsY=; b=MDSEm2HXDsjqXhZ5loUi+0pPWSUTcC1Mw0zD7AffT9QDP+wtFRtTgXA5PzBqZqZE84 h6i24u+olNA+qVPpLOt/XQ4ACHb/Kio63S/Zc0yoZo5q9GDX6F4L3yuXmY1gyT0erbqk sGDyEs+II2q3DJFZUGlsbsJFPaVXsiSwnuT+KBe869GavlC5LRpKWGvkHDJjJLuI/Jse LYQMxFIkwdW64gU02zWVWSbEOQWIlnsSiJTEf2Rtu6iGByp1pZTzysVECzJNtajR7kf4 +UwhvtSfHKV0nlao3VYVUtvbqsRweqcIFtvXWBlApGzQSAylEwciihe/gZCzFSsOnacW MCiw== 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:content-transfer-encoding; bh=JRDtfxa/q7/WfPcObl3GZoIQHK9I7lvS+uSXR8x1UsY=; b=QWozSNhsaYXm4XXNQw+vMtSwDPAwDFPUo34WmvshY7PjzB1C64xRFNaTYNA1JsmbOH FFMPHpJpx8MrxDrWfwxF5JWW9/ZXpcFQW6Ua4r98nSRt7n4MptYbtZOSqFLPtp3H7vfJ ZrL7sIdkyLWFHl8aNZw683nl5GRhlHA/BwLJZG1WTO9abXhVQZcRvm0JGZpcmebDoy6T +wCaihfG7o+rmeZv4HIlnVIDhmRlI9GuQc5Y3utIjf4enJKD2W2ix6L3vCutNpN6bqcg rj8Pqr4WLW9cRaTtqpaGXJGS2zYkUF1DwhXaGFd54W8bEU/2NFiQax+KFRSLbEQD2t2h CYQg== X-Gm-Message-State: AOUpUlG83aIlr4yo+VgHy1TQnFp2vHEvgWsZi3CdPNvDi95H7Yo9LCsA WW9gfLjMl6g3JcRNhZucecx9oPx2riwqiTNvz+w= X-Google-Smtp-Source: AAOMgpddRo3mC3IPBB4WLfijItEvu1tmr3xwYLG1aehgVM+qOWNF5/h9V62kuaY8OrQM3+vK+G4/6F+4iDOoQoKAMps= X-Received: by 2002:a19:9710:: with SMTP id z16-v6mr5497667lfd.17.1531503047093; Fri, 13 Jul 2018 10:30:47 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4010:c07::231 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:227354 Archived-At: >> 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=E2=80=94are 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.