[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1318425974.13262.26.camel@gandalf.stny.rr.com>
Date:	Wed, 12 Oct 2011 09:26:14 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates
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
-- Steve
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists
 
