From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: Merge 8xx to Linus tree?
Date: Sun, 17 Oct 2004 07:03:52 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0410170702410.3826@localhost.localdomain> (raw)
In-Reply-To: <20041014224128.GE19791@smtp.west.cox.net>
On Thu, 14 Oct 2004, Tom Rini wrote:
> On Thu, Oct 14, 2004 at 06:25:54PM -0400, Robert P. J. Day wrote:
> > what does this mean in terms of urgency in getting changes into the
> > 8xx stuff, then? does this imply a fixed window of opportunity in the
> > near future, or does it mean that once stuff starts to get moved
> > upstream, it will get moved on a regular basis? just curious.
>
> 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?
rday
next prev parent reply other threads:[~2004-10-17 11:11 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 [this message]
2004-10-17 12:30 ` Dale Farnsworth
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=Pine.LNX.4.60.0410170702410.3826@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=trini@kernel.crashing.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).