From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: rcu and locking trees unfetchable
Date: Mon, 26 May 2008 10:38:33 +0200 [thread overview]
Message-ID: <20080526083833.GA24419@elte.hu> (raw)
In-Reply-To: <20080526135444.f7cb038d.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Ingo,
>
> Fetching the rcu and locking trees failed this morning, so I have left
> them out of linux-next for today.
-tip tree is undergoing restructuring, the new branch structure is:
auto-ftrace-next [ relative to auto-ftrace-next-base ]
auto-sched-next [ relative to auto-sched-next-base ]
auto-x86-next [ relative to auto-x86-next-base ]
rcu got renamed to "core/rcu" - that will likely grow a -next postfix as
well. Locking got renamed to "core/locking" - that too will likely get a
-next topic branch as well. (but please use core/rcu and core/locking in
the meantime)
Ingo
next prev parent reply other threads:[~2008-05-26 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 3:54 linux-next: rcu and locking trees unfetchable Stephen Rothwell
2008-05-26 4:12 ` Stephen Rothwell
2008-05-26 8:38 ` Ingo Molnar [this message]
2008-05-27 0:50 ` Stephen Rothwell
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=20080526083833.GA24419@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).