From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Ian Lambert <ian.lambert_42@yahoo.com>
Subject: Re: setup release candidate - please test
Date: Wed, 17 May 2017 20:24:00 -0000 [thread overview]
Message-ID: <4f90e249-a700-2986-0ce0-68db5ab94cbf@dronecode.org.uk> (raw)
In-Reply-To: <d0b65c7f-246b-b871-d573-7a01480d53f0@dronecode.org.uk>
On 16/05/2017 15:06, Jon Turney wrote:
> On 16/05/2017 14:45, Ian Lambert wrote:
>> On May 16, 2017 6:52:17 AM EDT, Jon Turney <> wrote:
>>> On 15/05/2017 22:11, Brian Inglis wrote:
>>>> On 2017-05-15 14:42, Ian Lambert via cygwin wrote:
>>>>> On Mon, 5/15/17, Jon Turney wrote:
>>>>> On 15/05/2017 16:29, Ian Lambert via cygwin wrote:
>> When I try --user-agent=anything with setup, it quietly does nothing.
>
> I'm not sure if you missed or ignored that the wget option is referred
> to here.
>
>> It isn't an option, like proxy username and password aren't?
>
> Correct, it isn't an option. setup --help will confirm this for you.
>
> I don't know why unrecognized options aren't fatal errors.
So, I might have been misled by my low opinion of setup here:
> $ ./setup-x86_64 --user-agent=anything
>
> Error during option processing.
[...]
Can you give an example of a setup command line containing an invalid
option which "quietly does nothing" rather than reporting an error?
> Depending on the results of the tests suggested with wget, I may
> consider changing or removing the user-agent reported by cygwin setup,
> or providing such an option.
This snapshot adds a --user-agent option, which allows the user agent
string to be specified.
https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-05-17 19:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <129322595.2045958.1494880943500.ref@mail.yahoo.com>
2017-05-15 21:11 ` Ian Lambert via cygwin
2017-05-15 21:55 ` Brian Inglis
2017-05-16 11:10 ` Jon Turney
[not found] ` <3BE560BC-84EF-4C6D-8131-85A652C7B18E@yahoo.com>
2017-05-16 14:44 ` Jon Turney
2017-05-17 20:24 ` Jon Turney [this message]
2017-05-26 14:40 ` Jon Turney
[not found] <1680333473.595405.1495810914804.ref@mail.yahoo.com>
2017-05-26 17:06 ` Ian Lambert via cygwin
2017-05-26 19:35 ` Jon Turney
2017-05-26 20:34 ` Peter A. Castro
[not found] <229690283.739700.1494954490567.ref@mail.yahoo.com>
2017-05-16 17:22 ` Ian Lambert via cygwin
2017-05-17 6:18 ` Brian Inglis
[not found] <1118622054.582575.1494947930554.ref@mail.yahoo.com>
2017-05-16 16:55 ` Ian Lambert via cygwin
2017-05-16 17:08 ` Brian Inglis
[not found] <1287176650.1659138.1494862170535.ref@mail.yahoo.com>
2017-05-15 15:56 ` Ian Lambert via cygwin
2017-05-15 16:15 ` Jon Turney
2017-05-08 18:28 Eric Fahlgren
-- strict thread matches above, loose matches on Subject: below --
2017-05-08 11:11 Jon Turney
[not found] ` <CAG2dRtHsvRs-xTYN16Fw=OqUVAisQeMPFpppxV5E1pDsxMTVDg@mail.gmail.com>
2017-05-08 11:38 ` Dave Caswell via cygwin
2017-05-08 11:54 ` Jon Turney
2017-05-08 13:33 ` Henry S. Thompson
2017-05-08 17:37 ` Brian Inglis
2017-05-09 9:59 ` Jon Turney
2017-05-09 16:41 ` Brian Inglis
2017-05-09 19:37 ` Andrey Repin
2017-05-11 21:16 ` Jim Reisert AD1C
2017-05-08 11:49 ` Steven Penny via cygwin
2017-05-09 10:03 ` Jon Turney
2017-05-08 13:55 ` Eliot Moss
2017-05-09 11:22 ` Jon Turney
2017-05-09 13:37 ` Eliot Moss
2017-05-08 16:27 ` Ian Lambert via cygwin
2017-05-15 1:46 ` Jon Turney
2017-05-08 19:53 ` Peter A. Castro
2017-05-08 21:55 ` Jon Turney
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f90e249-a700-2986-0ce0-68db5ab94cbf@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=ian.lambert_42@yahoo.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.
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).