From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] tst_test.sh: Print tst_{res, brk} into stdout
Date: Sat, 20 Jun 2020 01:55:28 -0400 (EDT) [thread overview]
Message-ID: <104572215.16889120.1592632528302.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200619192542.20113-1-pvorel@suse.cz>
----- Original Message -----
> This allows printing messages on functions which output is redirected
> into variable or used in eval. Also this change unifies the behavior
> with C new API, which printed into stderr from the beginning.
Should the subject say "into stderr"? Other than that I'm OK
with the change.
next prev parent reply other threads:[~2020-06-20 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 19:25 [LTP] [RFC PATCH 1/1] tst_test.sh: Print tst_{res, brk} into stdout Petr Vorel
2020-06-20 5:55 ` Jan Stancek [this message]
2020-06-20 9:12 ` Petr Vorel
2020-06-22 8:53 ` Cyril Hrubis
2020-06-22 14:31 ` Petr Vorel
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=104572215.16889120.1592632528302.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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