From: Henning <xaoxx@t-online.de>
To: cygwin@cygwin.com
Subject: Re: setup.exe enhancement request, proceed on error after logging error to setup.log
Date: Tue, 11 Jun 2019 08:03:00 -0000 [thread overview]
Message-ID: <268983dc-b0fb-9c98-d920-0c0615b9c454@t-online.de> (raw)
In-Reply-To: <CAFWoy7FT1T7v=WOvKNRpz7vryCZ0SvYYooDmzH_HU06igu-yhA@mail.gmail.com>
On 10/06/2019 23:41, Keith Christian wrote:
>
> Would the maintainers (Achim? Jon?) be willing to consider an option
> box log errors to the setup.log file and "Skip non-fatal errors and
> continue?"
either this, or a prompt asking if the user wants to continue or abort.
Henning
--
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:[~2019-06-11 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:41 Keith Christian
2019-06-11 8:03 ` Henning [this message]
2019-06-11 11:28 ` Keith Christian
2019-06-11 15:24 ` Brian Inglis
2019-06-11 16:35 ` Andrey Repin
2019-06-11 17:19 ` Achim Gratz
2019-06-11 18:39 ` Brian Inglis
2019-06-11 20:52 ` Keith Christian
2019-06-12 13:01 ` Brian Inglis
2019-06-12 13:16 ` Keith Christian
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=268983dc-b0fb-9c98-d920-0c0615b9c454@t-online.de \
--to=xaoxx@t-online.de \
--cc=cygwin@cygwin.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).