From: Jens Axboe <axboe@kernel.dk>
To: Erwan Velu <erwan@enovance.com>
Cc: fio@vger.kernel.org
Subject: Re: Question about exec_string()
Date: Tue, 16 Jul 2013 15:13:33 -0600 [thread overview]
Message-ID: <20130716211333.GP22392@kernel.dk> (raw)
In-Reply-To: <51E5B4C6.9040705@enovance.com>
On Tue, Jul 16 2013, Erwan Velu wrote:
> On 16/07/2013 22:58, Jens Axboe wrote:
> >
> >I'll happily take a patch to include the output into the general logging
> >:-). That's the way it should work.
> That could be very verbose. Isn't that a problem ?
> I though to split it to let user read it later if needed instead of flooding
> the current console.
Sure, that'd be fine too. You could have jobname-prerun.txt etc created.
I'm fine with either approach.
--
Jens Axboe
prev parent reply other threads:[~2013-07-16 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 7:19 Question about exec_string() Erwan Velu
2013-07-16 20:58 ` Jens Axboe
2013-07-16 21:01 ` Erwan Velu
2013-07-16 21:13 ` Jens Axboe [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130716211333.GP22392@kernel.dk \
--to=axboe@kernel.dk \
--cc=erwan@enovance.com \
--cc=fio@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.