linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates
Date: Wed, 12 Oct 2011 18:23:20 +0200	[thread overview]
Message-ID: <20111012162320.GA31857@elte.hu> (raw)
In-Reply-To: <1318425974.13262.26.camel@gandalf.stny.rr.com>

* Steven Rostedt <rostedt@goodmis.org> wrote:

> On Wed, 2011-10-12 at 07:21 -0400, Steven Rostedt wrote:
> > [ Added hpa ]
> > 
> > On Wed, 2011-10-12 at 10:16 +0200, Ingo Molnar wrote:
> > >  
> > > > Please pull the latest tip/perf/core tree, which can be found at:
> > > > 
> > > >   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> > > > tip/perf/core
> > > > 
> > > > Head SHA1: d696b58ca2c3ca76e784ef89a7e0453d9b7ab187
> > > 
> > > Hm, even after 12+ hours of wait i can only pull 177e216 from your 
> > > tip/perf/core. Is this a korg delay, or did you forget to push? The 
> > > perf/urgent branch was there, so i don't think it's korg delay.
> > 
> > I just tried again, and got:
> > 
> > $ git push push trace/tip/perf/core:tip/perf/core
> > Enter passphrase for key '/home/rostedt/.ssh/id_rsa_korg': 
> > Everything up-to-date
> 
> > It seems that gitolite isn't refreshing rebases?
> 
> There seems to be issues with kernel.org refreshing. You can get the
> same branch at my github repo:
> 
>   git://github.com/rostedt/linux.git
> tip/perf/core
> 
> 
> It has the same SHA1: d696b58ca2c3ca76e784ef89a7e0453d9b7ab187

Got it from there - thanks Steve!

Tests are also looking good so far.

	Ingo

  reply	other threads:[~2011-10-12 16:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 15:20 [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates Steven Rostedt
2011-10-11 15:20 ` [PATCH 1/2 v2] tracing: Warn on output if the function tracer was found corrupted Steven Rostedt
2011-10-11 15:20 ` [PATCH 2/2 v2] tracing: Do not allocate buffer for trace_marker Steven Rostedt
2011-10-12  8:16 ` [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates Ingo Molnar
2011-10-12 11:21   ` Steven Rostedt
2011-10-12 13:26     ` Steven Rostedt
2011-10-12 16:23       ` Ingo Molnar [this message]
2011-10-12 16:32         ` Steven Rostedt
2011-10-13  8:59         ` Ingo Molnar
2011-10-13 13:55           ` Steven Rostedt
2011-10-13 14:00             ` Steven Rostedt

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=20111012162320.GA31857@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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).