From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Relics of removed dir-locals-file-2 feature in pretest
Date: Tue, 28 Nov 2017 19:51:45 +0200 [thread overview]
Message-ID: <83tvxe47gu.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY17HPKCi4r9d3GjssM8idGjir2v8x5CZH51qWDyUvagcA@mail.gmail.com> (message from Kaushal Modi on Tue, 28 Nov 2017 17:34:19 +0000)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Tue, 28 Nov 2017 17:34:19 +0000
> Cc: emacs-devel@gnu.org
>
> When I put that link in the message, I couldn't find any rules on how to do that in on
> http://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE?h=emacs-26 or
> https://www.gnu.org/prep/standards/html_node/Change-Logs.html.
>
> For contributing to the Org repo, the style is to mention links simply within angle brackets:
>
> <https://lists.gnu.org/r/emacs-devel/2017-11/msg00649.html>
>
> Example:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=d7940ae2a7ca01f01d17ba85e113ad7cc65b10ea
>
> Can the same rule be adopted for the Emacs repo and documented in /CONTRIBUTE?
Why is that important? It's a nuisance to remember to add the
brackets, so I'd prefer to avoid that.
next prev parent reply other threads:[~2017-11-28 17:51 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 [this message]
2017-11-28 17:59 ` Kaushal Modi
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=83tvxe47gu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
/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).