From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs-devel@gnu.org
Subject: Re: preferring https: to http: in commit messages for gnu.org
Date: Mon, 16 Oct 2017 18:09:03 +0300 [thread overview]
Message-ID: <83wp3vf7u8.fsf@gnu.org> (raw)
In-Reply-To: <494d6c88-bec0-9edc-a35b-32b59fedff05@cs.ucla.edu> (message from Paul Eggert on Mon, 16 Oct 2017 00:07:09 -0700)
> Cc: Emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 16 Oct 2017 00:07:09 -0700
>
> Eli Zaretskii wrote:
> > I cannot be responsible for every useful URL out there.
>
> The newly-added change does not check for every useful URL, only for URLs to
> gnu.org or fsf.org.
That includes URLs such as
http://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00592.html
doesn't it? This is by far the most frequent use of URLs in the
commit log messages for me: to cite discussions on our lists, since it
is not uncommon to have an issue be raised on a list, rather than via
the bug tracker. If you can amend the change to leave out URLs that
point to GNU mailing list messages, it's possible that what's left
will be insignificant noise for me. But I rather suspect that
lists.gnu.org pointers are one of your main targets...
> The goal is for developers to have reliable communications
> from the GNU project itself, even if other sources are less reliable.
Sorry, I cannot be responsible for the protocols supported by GNU list
servers. It is unreasonable to ask me to correct such references, or
risk to have my commits rejected.
> Without this change, I need to manually fix the gnu.org and fsf.org URLs in
> ChangeLog.<N>, which is an annoyance.
It is a similar annoyance to require me to do that when I need to cite
a mailing-list message.
> (Especially since many of these URLs are in my own commit
> messages. :-)
Well, you can always install such hooks locally, if that's the problem.
Thanks.
next prev parent reply other threads:[~2017-10-16 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 7:14 preferring https: to http: in commit messages for gnu.org Paul Eggert
2017-10-15 14:25 ` Eli Zaretskii
2017-10-16 7:07 ` Paul Eggert
2017-10-16 15:09 ` Eli Zaretskii [this message]
2017-10-16 15:19 ` Yuri Khan
2017-10-16 16:20 ` Robert Pluim
2017-10-16 18:47 ` Paul Eggert
2017-10-16 18:54 ` Eli Zaretskii
2017-10-16 23:15 ` Paul Eggert
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=83wp3vf7u8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).