unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Relics of removed dir-locals-file-2 feature in pretest
Date: Tue, 28 Nov 2017 17:59:05 +0000	[thread overview]
Message-ID: <CAFyQvY3YRJJSMZ2V8y90VtwyAV9mCrpo1xLQ64DbCyYE2+8+OA@mail.gmail.com> (raw)
In-Reply-To: <83tvxe47gu.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

On Tue, Nov 28, 2017 at 12:52 PM Eli Zaretskii <eliz@gnu.org> 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

[-- Attachment #2: Type: text/html, Size: 1415 bytes --]

  reply	other threads:[~2017-11-28 17:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 13:58 Relics of removed dir-locals-file-2 feature in pretest Kaushal Modi
2017-11-21 19:56 ` Kaushal Modi
2017-11-21 20:33   ` Eli Zaretskii
2017-11-21 21:11     ` Kaushal Modi
2017-11-22 15:19       ` Eli Zaretskii
2017-11-22 15:58         ` Kaushal Modi
2017-11-22 16:20           ` Eli Zaretskii
2017-11-22 16:28             ` Kaushal Modi
2017-11-23 15:53               ` Eli Zaretskii
2017-11-23 17:34                 ` Kaushal Modi
2017-11-23 20:08                   ` Eli Zaretskii
2017-11-27 14:57                     ` Kaushal Modi
2017-11-27 16:14                       ` Eli Zaretskii
2017-11-27 17:04                         ` Kaushal Modi
2017-11-27 17:27                           ` Eli Zaretskii
2017-11-27 17:50                             ` Kaushal Modi
2017-11-28 17:19                               ` Eli Zaretskii
2017-11-28 17:34                                 ` Kaushal Modi
2017-11-28 17:51                                   ` Eli Zaretskii
2017-11-28 17:59                                     ` Kaushal Modi [this message]
2017-11-28 20:02                                     ` Davis Herring
2017-11-28 20:36                                       ` Eli Zaretskii

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=CAFyQvY3YRJJSMZ2V8y90VtwyAV9mCrpo1xLQ64DbCyYE2+8+OA@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).