From: Seth Forshee <seth.forshee@canonical.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH trace-cmd 0/1] Makefile: Use CPPFLAGS from the environment
Date: Mon, 6 Jan 2014 13:36:52 -0600 [thread overview]
Message-ID: <20140106193652.GB1556@thinkpad-t410> (raw)
In-Reply-To: <20140106140753.55f3f3c7@gandalf.local.home>
On Mon, Jan 06, 2014 at 02:07:53PM -0500, Steven Rostedt wrote:
> On Mon, 6 Jan 2014 11:56:24 -0600
> Seth Forshee <seth.forshee@canonical.com> wrote:
>
> > Hi Steve,
> >
> > Here's another patch for trace-cmd that I'm using in Debian. Please
> > consider it for your tree.
> >
> > It also looks like you haven't applied the patches I sent a few months
> > back [1][2]. I'm guessing you just forgot about them, but please let me
> > know if there's something I need to fix. I also pushed out all of these
> > patches if you'd prefer to do a pull:
>
> I actually applied everything, and a lot more updates that I never
> pushed.
>
> Anyway, thanks! I applied this too and pushed it up.
Thanks!
There is something odd about the updates you pushed though. You've now
got a version 2.2.1 on your trace-cmd-stable-v2.2 branch, which used to
be tagged trace-cmd-v2.2.1, and another 2.2.1 on master which now has
that tag. I'm guessing that's not what you intended to do?
Seth
next prev parent reply other threads:[~2014-01-06 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 17:56 [PATCH trace-cmd 0/1] Makefile: Use CPPFLAGS from the environment Seth Forshee
2014-01-06 17:56 ` [PATCH trace-cmd 1/1] " Seth Forshee
2014-01-06 19:07 ` [PATCH trace-cmd 0/1] " Steven Rostedt
2014-01-06 19:36 ` Seth Forshee [this message]
2014-01-06 19:54 ` Steven Rostedt
2014-01-06 20:00 ` Steven Rostedt
2014-01-06 20:08 ` Seth Forshee
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=20140106193652.GB1556@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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