public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: tzanussi@gmail.com, linux-kernel@vger.kernel.org, fweisbec@gmail.com
Subject: Re: [PATCH 0/7] perf trace command-line cleanup
Date: Wed, 10 Nov 2010 08:32:36 +0100	[thread overview]
Message-ID: <20101110073236.GA29493@elte.hu> (raw)
In-Reply-To: <20101109213829.GB7883@ghostprotocols.net>


* Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:

> Ingo,
> 
> 	Please pull from Tom's git tree, I'm traveling and can't do
> further tests, but all seems cool improvements,

I cannot pull it - the tree is based against tip:master, and the patches sent in 
email wont apply.

Tom, mind rebasing your fixes to perf/urgent [which is really just Linus's latest 
tree right now], with Arnaldo's Acked-by added to each patch?

Thanks,

	Ingo

  reply	other threads:[~2010-11-10  7:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 21:18 [PATCH 0/7] perf trace command-line cleanup tzanussi
2010-11-09 21:18 ` [PATCH 1/7] perf trace scripting: fix some small memory leaks and missing error checks tzanussi
2010-11-09 21:18 ` [PATCH 2/7] perf trace scripting: remove system-wide param from shell scripts tzanussi
2010-11-09 21:18 ` [PATCH 3/7] perf record: make the record options available outside perf record tzanussi
2010-11-09 21:18 ` [PATCH 4/7] perf trace record: handle commands correctly tzanussi
2010-11-09 21:18 ` [PATCH 5/7] perf trace: live-mode command-line cleanup tzanussi
2010-11-09 21:18 ` [PATCH 6/7] perf trace: update Documentation with new perf trace variants tzanussi
2010-11-09 21:18 ` [PATCH 7/7] perf trace: update usage tzanussi
2010-11-09 21:38 ` [PATCH 0/7] perf trace command-line cleanup Arnaldo Carvalho de Melo
2010-11-10  7:32   ` Ingo Molnar [this message]
2010-11-10 18:09     ` Tom Zanussi

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=20101110073236.GA29493@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tzanussi@gmail.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