From: Jens Axboe <axboe@kernel.dk>
To: Erwan Velu <erwan@enovance.com>
Cc: fio@vger.kernel.org
Subject: Re: [Pull Request] Fixing coherency in fio2gnuplot
Date: Mon, 22 Jul 2013 14:58:16 -0600 [thread overview]
Message-ID: <51ED9CE8.8050203@kernel.dk> (raw)
In-Reply-To: <51ED9BA1.602@enovance.com>
On 07/22/2013 02:52 PM, Erwan Velu wrote:
> On 22/07/2013 20:29, Jens Axboe wrote:
>> On Mon, Jul 22 2013, Erwan Velu wrote:
>>> Hello,
>>> Sorry to make many pull request in a row but I just discover a serious
>>> problem when plotting multiple traces at the same time. It was in fact
>>> shortening the plots & rendering to the smallest trace file.
>>>
>>> This bug is pretty boring and this patch series does fix it.
>>> The branch is on top the current master, shall be easy to merge ;o)
>> No worries, pulled both of them. Thanks!
>>
> Thanks !
>
> Did you got the chance to had a look at it ?
The actual ouputs? No, not yet, will get around to playing with it
before the next release.
--
Jens Axboe
prev parent reply other threads:[~2013-07-22 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 17:46 [Pull Request] Fixing coherency in fio2gnuplot Erwan Velu
2013-07-22 18:29 ` Jens Axboe
2013-07-22 20:52 ` Erwan Velu
2013-07-22 20:58 ` 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=51ED9CE8.8050203@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.