From: Lucian Adrian Grijincu <lucian.grijincu@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] perf tools: Initial python binding
Date: Sun, 30 Jan 2011 00:39:15 +0000 (UTC) [thread overview]
Message-ID: <loom.20110130T013317-927@post.gmane.org> (raw)
In-Reply-To: <1296339559-20914-8-git-send-email-acme@infradead.org>
Arnaldo Carvalho de Melo <acme <at> infradead.org> writes:
> --- /dev/null
> +++ b/tools/perf/python/twatch.py
> @@ -0,0 +1,41 @@
> +#! /usr/bin/python
> +++ b/tools/perf/util/setup.py
> @@ -0,0 +1,18 @@
> +#!/usr/bin/python2
Shouldn't both of these be?
#!/usr/bin/env python
--
Lucian
next prev parent reply other threads:[~2011-01-30 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 22:19 [GIT PULL 0/7] perf/core improvements Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 1/7] perf record: No need to check for overwrites Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 2/7] perf events: Account PERF_RECORD_LOST events in event__process Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 3/7] perf evlist: Support non overwrite mode in perf_evlist__read_on_cpu Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 4/7] perf top: Switch to non overwrite mode Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 5/7] perf tools: Rename 'struct sample_data' to 'struct perf_sample' Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 6/7] perf tools: Kill event_t typedef, use 'union perf_event' instead Arnaldo Carvalho de Melo
2011-01-29 22:19 ` [PATCH 7/7] perf tools: Initial python binding Arnaldo Carvalho de Melo
2011-01-30 0:39 ` Lucian Adrian Grijincu [this message]
2011-01-30 13:44 ` Arnaldo Carvalho de Melo
2011-01-31 10:37 ` Ingo Molnar
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=loom.20110130T013317-927@post.gmane.org \
--to=lucian.grijincu@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®