From: Andy Wingo <wingo@pobox.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: 23349-done@debbugs.gnu.org
Subject: bug#23349: Compile output shall be error output
Date: Tue, 28 Feb 2017 16:07:39 +0100 [thread overview]
Message-ID: <87poi2l5fo.fsf@pobox.com> (raw)
In-Reply-To: <E07A8F00-F5B3-485E-AF1D-7E299374FA78@gmail.com> (Matt Wette's message of "Sat, 25 Jun 2016 13:54:25 -0700")
On Sat 25 Jun 2016 22:54, Matt Wette <matt.wette@gmail.com> writes:
> And I believe this works as asked. Below I execute the same “load” three times under guile, under bash: first two w/o “2>/dev/null”, and the third time with “2>/dev/null” . For the
> fourth time, I use “2>/dev/null -s ,update” to process as script (and skip the banner).
Thanks for checking. Closing as done; please follow up on the bug if
there is an error.
Andy
prev parent reply other threads:[~2017-02-28 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 11:36 bug#23349: Compile output shall be error output Jean Louis
2016-06-25 20:12 ` Matt Wette
2016-06-25 20:54 ` Matt Wette
2017-02-28 15:07 ` Andy Wingo [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87poi2l5fo.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=23349-done@debbugs.gnu.org \
--cc=matt.wette@gmail.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).