From: "Dale Farnsworth" <dale@farnsworth.org>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Merge 8xx to Linus tree?
Date: Sun, 17 Oct 2004 05:30:45 -0700 [thread overview]
Message-ID: <20041017123045.GA25808@xyzzy> (raw)
In-Reply-To: <Pine.LNX.4.60.0410170702410.3826@localhost.localdomain>
On Sun, Oct 17, 2004 at 11:03:52AM +0000, Robert P. J. Day wrote:
> > Once upstream, new changes won't (unless not-fully-baked) go into
> > linuxppc-2.5.
>
> um ... sorry, i'm still not sure what this means. does it mean that,
> at some point (to be determined/announced?), the linuxppc-2.5 tree
> will be put to the side, and all further mods should be done directly
> against the 2.5 tree?
Yes, that's already the case for most ppc platforms. The only thing
that keeps it from being true for 8xx is that it doesn't work yet
in the linux-2.5 tree.
-Dale
next prev parent reply other threads:[~2004-10-17 12:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 14:53 Merge 8xx to Linus tree? Joakim Tjernlund
2004-10-14 22:16 ` Tom Rini
2004-10-14 22:29 ` Joakim Tjernlund
2004-10-14 22:25 ` Robert P. J. Day
2004-10-14 22:41 ` Tom Rini
2004-10-17 11:03 ` Robert P. J. Day
2004-10-17 12:30 ` Dale Farnsworth [this message]
2004-10-18 3:21 ` Dan Malek
2004-10-18 14:49 ` Tom Rini
2004-10-15 8:16 ` Robert P. J. Day
2004-10-29 12:07 ` Joakim Tjernlund
2004-10-29 12:12 ` Pantelis Antoniou
2004-10-29 12:27 ` Joakim Tjernlund
2004-10-29 12:54 ` Pantelis Antoniou
2004-10-29 14:22 ` Tom Rini
2004-10-29 14:23 ` Pantelis Antoniou
2004-10-29 14:35 ` Joakim Tjernlund
2004-10-29 14:49 ` Tom Rini
2004-10-29 14:53 ` Joakim Tjernlund
2004-10-29 14:19 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 14:44 Rune Torgersen
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=20041017123045.GA25808@xyzzy \
--to=dale@farnsworth.org \
--cc=linuxppc-embedded@ozlabs.org \
/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).