[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1318418515.13262.21.camel@gandalf.stny.rr.com>
Date: Wed, 12 Oct 2011 07:21:55 -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
[ 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
$ git log -1 --pretty=oneline trace/tip/perf/core
d696b58ca2c3ca76e784ef89a7e0453d9b7ab187 tracing: Do not allocate buffer for tra
But if I refresh from git itself
$ git remote -v
ftrace git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git (fetch)
ftrace git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git (push)
push gitolite@...kernel.org:/pub/scm/linux/kernel/git/rostedt/linux-trace.git (fetch)
push gitolite@...kernel.org:/pub/scm/linux/kernel/git/rostedt/linux-trace.git (push)
$ git remote update ftrace
Fetching ftrace
$ git log -1 --pretty=oneline ftrace/tip/perf/core
87912fdfc1378a7e7e54a169ef9eebeafa1af04f tracing: Do not allocate buffer for tra
It seems that gitolite isn't refreshing rebases?
I just pushed it to tip/perf/core-2. I waited about 5 minutes, and I
still do not see it.
The urgent branch I pushed the same time as I did the first version of
this branch.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists