From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: wget -q in bootstrap is too silent
Date: Sun, 6 Oct 2019 16:29:39 +0200 [thread overview]
Message-ID: <9e287312-78f4-8668-982a-299ea5241057@gmx.de> (raw)
In-Reply-To: <523aac74-12a8-1e17-2bc5-f4b1eef166ef@cs.ucla.edu>
[-- Attachment #1.1: Type: text/plain, Size: 406 bytes --]
Thank you, Paul !
On 06.10.19 06:38, Paul Eggert wrote:
> On 10/4/19 8:34 AM, Tim Rühsen wrote:
>> Instead of -q we could use -nv to avoid disguising the real error.
>> But there will be some diagnostic noice...
>
> At this point the bootstrap script is so noisy that a bit more won't
> hurt, especially if it's in a good cause. Thanks for reporting the
> problem; I installed the attached.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-10-06 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 15:34 wget -q in bootstrap is too silent Tim Rühsen
2019-10-06 4:38 ` Paul Eggert
2019-10-06 14:29 ` Tim Rühsen [this message]
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e287312-78f4-8668-982a-299ea5241057@gmx.de \
--to=tim.ruehsen@gmx.de \
--cc=bug-gnulib@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.
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).