From: Paul Mackerras <paulus@samba.org>
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Which Git Tree to pull from?
Date: Wed, 25 Jul 2007 11:14:51 +1000 [thread overview]
Message-ID: <18086.41995.642267.580108@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D9010895F78D@EMPBEDEX.empirix.com>
Morrison, Tom writes:
> I am a little confused here. I've been working in an older (2.6.11)
>
> ppc release and haven't been paying much attention to where I
>
> should be getting the latest / stable git tree (for powerpc).
>
>
>
> I am working on an e500/8548 branch - it looks like Kumar's
>
> Git tree looks relatively new with lots of new patches...?
Unlike the bad old days when stuff used to accumulate for ages in
various trees without getting merged into Linus' tree, these days
stuff gets merged into Linus' tree and released in the official
releases pretty promptly. So Linus' releases are the canonical ones
for powerpc.
I have a tree where I put stuff that will be going to Linus at the
next opportunity, but currently it is identical to Linus' tree. It
doesn't accumulate any long-term difference from Linus' tree.
Kumar's tree currently has some stuff for 8xxx pci support that looks
to have missed the merge window that just closed. If you want that
specific stuff you can use his tree. That stuff should get merged
into Linus' tree once 2.6.23 has been released.
Paul.
prev parent reply other threads:[~2007-07-25 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 12:21 Which Git Tree to pull from? Morrison, Tom
2007-07-24 14:10 ` Kumar Gala
2007-07-25 1:14 ` Paul Mackerras [this message]
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=18086.41995.642267.580108@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tmorrison@empirix.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