From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: Relics of removed dir-locals-file-2 feature in pretest Date: Tue, 28 Nov 2017 17:59:05 +0000 Message-ID: References: <833757cqy7.fsf@gnu.org> <83tvxmbat5.fsf@gnu.org> <83lgiyb801.fsf@gnu.org> <83d149at4o.fsf@gnu.org> <831skobvvw.fsf@gnu.org> <83r2sj66m6.fsf@gnu.org> <83h8tf638h.fsf@gnu.org> <83y3mq48xx.fsf@gnu.org> <83tvxe47gu.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c135c9cf2f30d055f0ec6c2" X-Trace: blaine.gmane.org 1511891979 2462 195.159.176.226 (28 Nov 2017 17:59:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 28 Nov 2017 17:59:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 28 18:59:33 2017 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 1eJkAE-0007zC-OV for ged-emacs-devel@m.gmane.org; Tue, 28 Nov 2017 18:59:22 +0100 Original-Received: from localhost ([::1]:39401 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eJkAL-0000qq-UT for ged-emacs-devel@m.gmane.org; Tue, 28 Nov 2017 12:59:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37616) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eJkAB-0000pL-1U for emacs-devel@gnu.org; Tue, 28 Nov 2017 12:59:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eJkAA-0005xG-7B for emacs-devel@gnu.org; Tue, 28 Nov 2017 12:59:19 -0500 Original-Received: from mail-yb0-x233.google.com ([2607:f8b0:4002:c09::233]:34886) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eJkA8-0005wv-LN; Tue, 28 Nov 2017 12:59:16 -0500 Original-Received: by mail-yb0-x233.google.com with SMTP id b186so300873yba.2; Tue, 28 Nov 2017 09:59:16 -0800 (PST) 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=I43cC2ndohn0LYGhAeSl5EgmFZ63MIgbjTn4r8XvAYM=; b=USB/9GIFVpkv+QCyzZ5AVgfwduBYTXvGpGpyrB6Yzsobvjh0s5BRFS8h9bGpVSFe1Z kQusZBZg7fEuQNG8RxkLPhsDMh988k52L/5EFzcadi+3zymxrId/reqrLPOQFmDCUIXS FC5G64p+p/tylmeWuOlyljGad275zIncY6wwfTmXgmQ1FCj6z7wJ8jU1D4sLJU3jjivS eTVJbs+gxKRuVdHO5ZOD8vGeETa5PBlH9EIIDwXz/IHbrjV1VUX4bHEC3HQxXiQEQ5tn jrUI4+mykM7Q3Ru2ET3WfGkXfZ9EIDZ2HmG8cjTugGYPyq/e4uWqvT+2lqpLB/RlLpth HbbQ== 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=I43cC2ndohn0LYGhAeSl5EgmFZ63MIgbjTn4r8XvAYM=; b=dDfCFLTEmOrYwTp935es6X4q+nUqT+MgFwZLFNGmn71D+kPqQwNTyk6kZVoaOJeoeH EAc5iKE46mb5w0huYKfaAJAQbPdLAQZYuzhvVwhT+LsZqP9kv0PCJO5p0PaLcv2bI8Sq PajAWO+4LjoJzxVWr1DqZucZEm2BChFi5iFf4ApIoo2XVJQl+jPkV3n4nhpX8f6Vvf6m m1lgi/LjFT4mXplWMCfiJ7WmGAS+pc/+dqoUX+lj/pXulRVHpfhFgsND6NU1qUO1m8sa uv+vOt5l32E5m6gXf8cOr4ousZf+0958hABZBkx5NDAmwTRXXsTxJQfexPQQuyPdptKw 5TWQ== X-Gm-Message-State: AJaThX7GQIAJ1zX913m5DpVyQqsjz1BI+GJEz5sW09u4JTTJoXiGNxk2 QPP2IomI4dURWsSvNl0Hqjc8wvYSTLne8G6oPRw= X-Google-Smtp-Source: AGs4zMZ+sb2ihDuly/5sgMv5VDjy8UNCs3+tNdy5FjgEzJ7VXuC1LyDChmtnj/awnUyl2DfGK4EbFXl6jQiGrkVHwWE= X-Received: by 10.37.161.1 with SMTP id z1mr12262566ybh.499.1511891955542; Tue, 28 Nov 2017 09:59:15 -0800 (PST) In-Reply-To: <83tvxe47gu.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4002:c09::233 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:220505 Archived-At: --94eb2c135c9cf2f30d055f0ec6c2 Content-Type: text/plain; charset="UTF-8" On Tue, Nov 28, 2017 at 12:52 PM Eli Zaretskii wrote: > Why is that important? It just brings in some consistency.. just as there are rules for other parts in the commit message. It also makes commit messages easily parseable (if ever needed) for links. > It's a nuisance to remember to add the > brackets, so I'd prefer to avoid that. > I have used that style in Org commits many times, and it's kind of become a second nature, so not very difficult to remember if doing that is added as a guideline to CONTRIBUTE in the "** Commit messages" section. Also, the "remembering issue" applies to everything else in that same section too :) But in any case, I thought of bringing this up as I saw that there were no guidelines on how to put links in commit messages. -- Kaushal Modi --94eb2c135c9cf2f30d055f0ec6c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Nov 28= , 2017 at 12:52 PM Eli Zaretskii <eliz@g= nu.org> wrote:
Why is that important?

It just brings = in some consistency.. just as there are rules for=20 other parts in the commit message. It also makes commit messages easily=20 parseable (if ever needed) for links.
=C2=A0
=C2=A0 It's a nui= sance to remember to add the
brackets, so I'd prefer to avoid that.

<= div>I have used that style in Org commits many times, and it's kind of = become a second nature, so not very difficult to remember if doing that is = added as a guideline to CONTRIBUTE in the "** Commit messages" se= ction. Also, the "remembering issue" applies to everything else i= n that same section too :)

But in any case, I = thought of bringing this up as I saw that there were no guidelines on how t= o put links in commit messages.
--
<= p dir=3D"ltr">Kaushal Modi

--94eb2c135c9cf2f30d055f0ec6c2--