From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] perf: Suggest inbuilt commands for unknown command
Date: Wed, 20 Mar 2024 12:44:26 -0300 [thread overview]
Message-ID: <ZfsEWoi6eevwLRQC@x1> (raw)
In-Reply-To: <ZfsDtr5ejAwGySOR@x1>
On Wed, Mar 20, 2024 at 12:41:45PM -0300, Arnaldo Carvalho de Melo wrote:
> ⬢[acme@toolbox perf-tools-next]$ perf raccord
> perf: 'raccord' is not a perf-command. See 'perf --help'.
This works with the second patch.
- Arnaldo
> ⬢[acme@toolbox perf-tools-next]$ perf ricord
> perf: 'ricord' is not a perf-command. See 'perf --help'.
>
> Did you mean this?
> record
> ⬢[acme@toolbox perf-tools-next]$ perf ricord
> perf: 'ricord' is not a perf-command. See 'perf --help'.
>
> Did you mean this?
> record
> ⬢[acme@toolbox perf-tools-next]$
>
> So I'll add that and go on from there.
>
> - Arnaldo
next prev parent reply other threads:[~2024-03-20 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 20:13 [PATCH v2 1/2] perf: Suggest inbuilt commands for unknown command Ian Rogers
2024-03-01 20:13 ` [PATCH v2 2/2] perf help: Lower levenshtein penality for deleting character Ian Rogers
2024-03-20 14:54 ` [PATCH v2 1/2] perf: Suggest inbuilt commands for unknown command Arnaldo Carvalho de Melo
2024-03-20 15:00 ` Arnaldo Carvalho de Melo
2024-03-20 15:12 ` Ian Rogers
2024-03-20 15:20 ` Arnaldo Carvalho de Melo
2024-03-20 15:25 ` Ian Rogers
2024-03-20 15:32 ` Arnaldo Carvalho de Melo
2024-03-20 15:40 ` Ian Rogers
2024-03-20 15:41 ` Arnaldo Carvalho de Melo
2024-03-20 15:44 ` Arnaldo Carvalho de Melo [this message]
2024-03-20 17:07 ` Ian Rogers
2024-03-20 19:34 ` Arnaldo Carvalho de Melo
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=ZfsEWoi6eevwLRQC@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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.