From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Terren Chow <terren.chow@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Questions about powerpc kernel tree
Date: Tue, 10 Aug 2010 14:19:18 +1000 [thread overview]
Message-ID: <1281413958.28245.17.camel@pasglop> (raw)
In-Reply-To: <AANLkTinqKv1OXDBtQfg0jOyw=04FQcAvoE8CPmMN7M5_@mail.gmail.com>
On Tue, 2010-08-10 at 10:39 +0800, Terren Chow wrote:
> Hi Ben:
> I'm not quite clearly know about the powerpc kernel tree histroy.
> why the tags in the powerpc kernel tree are only update to 2.6.26-rc9
> at about 2 years ago?
Not sure what you're looking at but your shouldn't need to use the
"powerpc kernel tree" whatever tree this is :-) All our work goes into
Linus tree on a regular basis, so unless you are specifically looking at
the powerpc "next" git branch aimed at the next merge window, there
should be nothing of interest to you there.
Ben.
next prev parent reply other threads:[~2010-08-10 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 2:39 Questions about powerpc kernel tree Terren Chow
2010-08-10 4:19 ` Benjamin Herrenschmidt [this message]
2010-08-14 4:21 ` Terren Chow
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=1281413958.28245.17.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=terren.chow@gmail.com \
/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).