From: Peter Zijlstra <peterz@infradead.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Fr??d??ric Weisbecker <fweisbec@gmail.com>
Subject: Re: tools/perf: libraries must come after objects
Date: Mon, 22 Feb 2010 14:48:59 +0100 [thread overview]
Message-ID: <1266846539.6122.132.camel@laptop> (raw)
In-Reply-To: <alpine.LSU.2.01.1002221430440.23762@obet.zrqbmnf.qr>
On Mon, 2010-02-22 at 14:31 +0100, Jan Engelhardt wrote:
>
> Do happen to have that as a faster git:// too?
>
git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
prev parent reply other threads:[~2010-02-22 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 0:24 tools/perf: libraries must come after objects Jan Engelhardt
2010-02-22 10:50 ` Ingo Molnar
2010-02-22 13:31 ` Jan Engelhardt
2010-02-22 13:47 ` Ingo Molnar
2010-02-23 23:54 ` Jan Engelhardt
2010-02-22 13:48 ` Peter Zijlstra [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=1266846539.6122.132.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jengelh@medozas.de \
--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