From: Zack Weinberg <zackw@panix.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: Fri, 22 Sep 2017 08:13:02 -0400 [thread overview]
Message-ID: <CAKCAbMh5BWBLzJadO1hFWWToUe9-sAJPiFGPr615W2_1meHbBA@mail.gmail.com> (raw)
In-Reply-To: <18cce39e-4a5a-27d8-a1ca-5ec45973088e@cs.ucla.edu>
Regarding the second patch, updates to config.sub, config.guess, and
move-if-change look fine to me, but the texinfo.tex update changes
enough unrelated stuff that I'd like you to test build the PDF version
of the manual and make sure nothing broke. (Cosmetic changes are
fine.)
zw
next prev parent reply other threads:[~2017-09-22 12:13 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
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 [this message]
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=CAKCAbMh5BWBLzJadO1hFWWToUe9-sAJPiFGPr615W2_1meHbBA@mail.gmail.com \
--to=zackw@panix.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).