From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Prefer https: for GNU and FSF URLs
Date: Mon, 9 Sep 2019 16:28:39 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1909091627190.23764@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1c22e434-1091-dba1-7604-c1e909ecef8a@cs.ucla.edu>
On Sat, 7 Sep 2019, Paul Eggert wrote:
> I was puzzled because you patched these three files when updating copyright
> dates in January, whereas I couldn't patch them today without fixing their
> trailing-newline style. I guess the pre-commit hooks have changed since
> January, but I don't know where they're kept.
Yes, we switched to using the AdaCore set of hooks, which must have some
differences from the old hooks in exactly how they detect problems with
trailing whitespace.
https://sourceware.org/ml/libc-alpha/2019-04/msg00335.html
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-09-09 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 4:24 [PATCH] Prefer https: for GNU and FSF URLs Paul Eggert
2017-09-22 11:47 ` Joseph Myers
2019-09-07 10:06 ` Paul Eggert
2019-09-07 10:22 ` Paul Eggert
2019-09-09 16:28 ` Joseph Myers [this message]
2019-09-09 17:45 ` Florian Weimer
2019-09-09 16:27 ` Joseph Myers
2019-09-09 21:18 ` Paul Eggert
2017-09-22 12:13 ` Zack Weinberg
2017-09-29 15:37 ` Maciej W. Rozycki
2017-09-29 16:59 ` Jonathan Nieder
2017-10-04 23:19 ` Maciej W. Rozycki
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/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1909091627190.23764@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.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.
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).