From: Jens Axboe <axboe@kernel.dk>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH] blktrace: document -k option
Date: Wed, 22 May 2013 07:51:02 +0000 [thread overview]
Message-ID: <20130522075102.GB9714@kernel.dk> (raw)
In-Reply-To: <518B0355.3030905@redhat.com>
On Thu, May 09 2013, Eric Sandeen wrote:
> On 5/9/13 9:00 AM, Jeff Moyer wrote:
> > Eric Sandeen <sandeen@redhat.com> writes:
> >
> >> The -k option was missing from the usage() output and was present
> >> only in the man page synopsis. Say a few more words about it.
> >>
> >
> > Hmm. See:
> >
> > commit fb7f86674a516ddff0d60bfab3bd284a4812075f
> > Author: Edward Shishkin <edward@redhat.com>
> > Date: Tue Apr 20 15:41:14 2010 +0200
> >
> > blktrace: disable kill option - take 2
> >
>
> Gah. That's clever.
>
> Then I guess it should be removed from the synopsis too.
>
> Shouldn't it have been removed from the actual code as well?
>
> Thanks though :)
Kill away :-)
--
Jens Axboe
prev parent reply other threads:[~2013-05-22 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 2:00 [PATCH] blktrace: document -k option Eric Sandeen
2013-05-09 14:00 ` Jeff Moyer
2013-05-09 18:38 ` Eric Sandeen
2013-05-22 7:51 ` 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=20130522075102.GB9714@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-btrace@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 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 NNTP newsgroup(s).