From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: perf: relative path to source for perf probe?
Date: Thu, 13 May 2010 14:36:23 -0300 [thread overview]
Message-ID: <20100513173623.GL19192@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTimLKfPHI81K_-N7gIkDXgenqOzNQlTvGFlCutvi@mail.gmail.com>
Em Thu, May 13, 2010 at 05:51:45PM +0200, Chase Douglas escreveu:
> On Thu, May 13, 2010 at 4:58 PM, Arnaldo Carvalho de Melo
> <acme@ghostprotocols.net> wrote:
> > Probably you won't find this if you look at the old 2.6.34 codebase
> > (yay, for tools/perf it is already hundreds of patches behind :-)), so
> > I recomend you look at what we have in linux-2.6-tip, branch
> > tip/perf/core, what is in 2.6.34 is in tip/perf/urgent and right now,
> > IIRC, just a one patch that is not in 2.6.34 proper, a cherry-pick from
> > tip/perf/core, no less :-)
>
> Where are these branches? I've looked at:
>
> http://git.kernel.org/?p=linux/kernel/git/acme/linux-2.6.git;a=summary
>
> but I don't see these branches listed.
Well, if you decide to go from my tree, its all in the "perf" branch,
but I'd recommend you follow Ingo, my git tree, at the moment, is just a
conduit to get things out to him, which happens without noticeable delay
once I send a pull request.
> Thanks for the pointers!
You're welcome, please let us know about any other thing we may be of
help to make you of help to us ;-)
> -- Chase
next prev parent reply other threads:[~2010-05-13 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 14:13 perf: relative path to source for perf probe? Chase Douglas
2010-05-13 14:58 ` Arnaldo Carvalho de Melo
2010-05-13 15:51 ` Chase Douglas
2010-05-13 17:36 ` Arnaldo Carvalho de Melo [this message]
2010-05-13 16:01 ` Chase Douglas
2010-05-13 17:34 ` Arnaldo Carvalho de Melo
2010-05-13 21:23 ` Masami Hiramatsu
2010-05-13 21:46 ` Arnaldo Carvalho de Melo
2010-05-13 22:10 ` Chase Douglas
2010-05-13 22:11 ` Masami Hiramatsu
2010-05-13 21:00 ` Masami Hiramatsu
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=20100513173623.GL19192@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=chase.douglas@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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