linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Peter Feiner <pfeiner@google.com>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH] perf trace: fix documentation for -i
Date: Thu, 5 Nov 2015 12:14:17 -0200	[thread overview]
Message-ID: <20151105141417.GB2539@redhat.com> (raw)
In-Reply-To: <1446657706-14518-1-git-send-email-pfeiner@google.com>

Em Wed, Nov 04, 2015 at 09:21:46AM -0800, Peter Feiner escreveu:
> The -i flag was incorrectly listed as a short flag for --no-inherit.
> It should have only been listed as a short flag for --input.
> 
> This documentation error has existed since the --input flag was
> introduced in 6810fc915f7a89d8134edb3996dbbf8eac386c26 (perf trace:
> Add option to analyze events in a file versus live).

Thanks, applied.

  reply	other threads:[~2015-11-05 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 17:21 [PATCH] perf trace: fix documentation for -i Peter Feiner
2015-11-05 14:14 ` Arnaldo Carvalho de Melo [this message]
2015-11-08  7:30 ` [tip:perf/urgent] perf trace: Fix " tip-bot for Peter Feiner

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=20151105141417.GB2539@redhat.com \
    --to=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfeiner@google.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 NNTP newsgroup(s).