From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 3/4] Don't write LOG_BABBLE output to stdout
Date: Mon, 02 Mar 2015 16:29:00 -0000 [thread overview]
Message-ID: <20150302162942.GC12754@calimero.vinschen.de> (raw)
In-Reply-To: <1425304525-12268-4-git-send-email-jon.turney@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On Mar 2 13:55, Jon TURNEY wrote:
> It somewhat hampers the use of setup as a command line tool that it writes
> everything to stdout. Don't write LOG_BABBLE output to stdout. Add '--verbose'
> flag to restore the previous behaviour.
>
> ChangeLog:
>
> 2015-03-02 Jon TURNEY <...>
>
> * LogFile.cc (VerboseOutput): Add option.
> (endEntry): Only write LOG_PLAIN to stdout, unless VerboseOutput.
Good idea, go ahead.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-02 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 13:55 [PATCH setup 0/4] Setup misc patches Jon TURNEY
2015-03-02 13:55 ` [PATCH setup 1/4] Fix truncation of "Bin?" and "Src?" column headers Jon TURNEY
2015-03-02 15:58 ` Corinna Vinschen
2015-03-02 13:55 ` [PATCH setup 2/4] Add a 'Retry' button to the IDD_FILE_INUSE dialog Jon TURNEY
2015-03-02 16:28 ` Corinna Vinschen
2015-03-02 13:55 ` [PATCH setup 3/4] Don't write LOG_BABBLE output to stdout Jon TURNEY
2015-03-02 16:29 ` Corinna Vinschen [this message]
2015-03-02 13:56 ` [PATCH setup 4/4] Remove msg() from LogFile::endEntry() Jon TURNEY
2015-03-02 16:32 ` Corinna Vinschen
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=20150302162942.GC12754@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@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).