From: Matt Porter <mporter@kernel.crashing.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 4xx ports
Date: Fri, 14 Nov 2003 08:28:54 -0700 [thread overview]
Message-ID: <20031114082854.A23689@home.com> (raw)
In-Reply-To: <3FB4D07C.4010909@jonmasters.org>; from jonathan@jonmasters.org on Fri, Nov 14, 2003 at 12:54:20PM +0000
On Fri, Nov 14, 2003 at 12:54:20PM +0000, Jon Masters wrote:
>
>
> Hi there,
>
> Several people seem to think I was after advice on a port to use or
> asking for help doing one etc.
>
> For the record I am not in this current thread of conversation asking
> for those things but I am trying to find out how we can get the stock
> official kernel distributed by kernel.org to reflect some of the changes
> which have been made.
Post patches versus the BK linux-2.4 tree here so they can be discussed.
If they are suitable for merging upstream (Paul is happy) then they will
be moved into the for-marcelo-ppc tree. This is a slow process unless
the changes are straightforward bug fixes or cleanups.
Merging patches into linuxppc-2.4 is much quicker and allows a wider
audience to test significant changes to help determine if they are
suitable to go upstream. Stuff will get merged from linuxppc-2.4
upstream over time.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-14 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 12:54 4xx ports Jon Masters
2003-11-14 15:28 ` Matt Porter [this message]
2003-11-14 17:16 ` Dan Kegel
2003-11-15 0:32 ` Jon Masters
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=20031114082854.A23689@home.com \
--to=mporter@kernel.crashing.org \
--cc=jonathan@jonmasters.org \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.