public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] trace-view: Add trace-view python wrapper
Date: Mon, 04 Jan 2010 20:22:17 -0800	[thread overview]
Message-ID: <4B42BE79.9090802@us.ibm.com> (raw)
In-Reply-To: <1262661789.28171.692.camel@gandalf.stny.rr.com>

Steven Rostedt wrote:
> On Mon, 2010-01-04 at 17:24 -0800, Darren Hart wrote:
>> The following patch series wraps the C trace-view-store for use with Python.
>>
>> Please pull the latest for-rostedt/trace-view git tree from:
>>
>>    git://git.kernel.org/pub/scm/linux/kernel/git/dvhart/trace-cmd.git for-rostedt/trace-view
>>
>>
>> (Apologies if this series arrives twice, I seem to be experiencing relay
>> issues).
> 
> Thanks, but you never pushed this up to kernel.org. I've applied them on
> a temp branch and they work after fixing some conflicts with commits I
> made.
> 
> If you want, I can just push that back out, but that will require you to
> do a rebase. But if I do another pull from you, I'll just have to
> resolve the conflicts again.
> 

I guess in on-going relay issues I missed the "git push". If you don't 
mind just sending them back to me I'll push your version to my 
kernal.org repo so you don't have to repeat the merge. Sorry about that.

The patches still haven't hit LKML from what I can tell...

Thanks,

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team

      reply	other threads:[~2010-01-05  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1262654682-20325-1-git-send-email-dvhltc@us.ibm.com>
2010-01-05  3:23 ` [PATCH 0/3] trace-view: Add trace-view python wrapper Steven Rostedt
2010-01-05  4:22   ` Darren Hart [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=4B42BE79.9090802@us.ibm.com \
    --to=dvhltc@us.ibm.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