From: Jiri Olsa <jolsa@redhat.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH 0/9] Tesstsuite - splitted to more commits
Date: Tue, 15 Dec 2015 13:03:52 +0100 [thread overview]
Message-ID: <20151215120352.GC5074@krava.brq.redhat.com> (raw)
In-Reply-To: <1449514372.24573.250.camel@redhat.com>
On Mon, Dec 07, 2015 at 07:52:52PM +0100, Michael Petlan wrote:
> Hi,
>
> so I have splitted the suite into more commits that are related to
> the logical parts of it. These patches should apply to the latest
> Arnaldo's tree on top of perf/core branch.
>
> I hope it works now.
> Thanks for reviewing.
patches 1-9 do not reference 0/9 id in In-Reply-To header,
so they all appear as independent emails
thanks,
jirka
next prev parent reply other threads:[~2015-12-15 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 18:52 [PATCH 0/9] Tesstsuite - splitted to more commits Michael Petlan
2015-12-15 12:03 ` Jiri Olsa [this message]
2015-12-16 11:59 ` Michael Petlan
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=20151215120352.GC5074@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.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;
as well as URLs for NNTP newsgroup(s).