From: John Traill <john.traill@motorola.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
Dan Malek <dan@embeddededge.com>, Wolfgang Denk <wd@denx.de>,
Tom Rini <trini@kernel.crashing.org>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: board specific defines in commproc.h !?!?
Date: Fri, 21 Jun 2002 15:18:04 +0100 [thread overview]
Message-ID: <3D13359C.2030803@motorola.com> (raw)
In-Reply-To: 15635.12386.415897.593660@argo.ozlabs.ibm.com
Everyone/Anyone,
Does this mean linuxppc_2_4_devel will disappear leaving a 2.4 stable tree and a 2.5 devel ?
Paul Mackerras wrote:
> Steven Scholz writes:
>
>
>>I am not quite sure about the policies now. Could you please explain:
>>
>>linuxppc_2_4 is a stable tree
>>linuxppc_2_4_devel is a devel tree
>>linuxppc_2_5 is a devel tree
>>
>>Is that right?
>
>
> 2_4_devel is stabilizing. Once 2.4.19 comes out the plan is to
> restructure the linuxppc_2_4 tree along the lines of the 2_4_devel
> tree and start moving the stuff from 2_4_devel into 2_4 and submit it
> to Marcelo.
>
> With 2.5, I am hoping to be able to keep Linus' tree in closer sync
> with our linuxppc-2.5 tree than we managed in the past with the 2_4
> trees.
>
> Paul.
>
--
Regards, John
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-21 14:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 9:20 board specific defines in commproc.h !?!? Steven Scholz
2002-06-17 14:05 ` John W. Linville
2002-06-17 15:32 ` Tom Rini
2002-06-17 15:37 ` Steven Scholz
2002-06-17 15:49 ` Tom Rini
2002-06-17 16:01 ` Steven Scholz
2002-06-17 16:28 ` Tom Rini
2002-06-17 17:25 ` Wolfgang Denk
[not found] ` <20020617173550.GV13541@opus.bloom.county>
2002-06-17 17:46 ` Steven Scholz
2002-06-17 20:23 ` Wolfgang Denk
[not found] ` <3D106922.7026437A@imc-berlin.de>
2002-06-19 15:05 ` Tom Rini
2002-06-19 15:18 ` Steven Scholz
2002-06-19 15:25 ` Tom Rini
2002-06-19 15:33 ` Steven Scholz
2002-06-19 15:41 ` Tom Rini
2002-06-19 15:47 ` Steven Scholz
2002-06-19 15:51 ` Tom Rini
2002-06-19 21:11 ` Dan Malek
2002-06-19 21:22 ` Tom Rini
2002-06-20 16:32 ` Dan Malek
2002-06-19 22:15 ` Wolfgang Denk
2002-06-19 23:26 ` Conn Clark
2002-06-20 16:40 ` Dan Malek
[not found] ` <3D12F140.23BA447F@imc-berlin.de>
[not found] ` <15635.12386.415897.593660@argo.ozlabs.ibm.com>
2002-06-21 14:18 ` John Traill [this message]
[not found] <20020617214339.GZ13541@opus.bloom.county>
2002-06-17 22:28 ` Wolfgang Denk
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=3D13359C.2030803@motorola.com \
--to=john.traill@motorola.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=steven.scholz@imc-berlin.de \
--cc=trini@kernel.crashing.org \
--cc=wd@denx.de \
/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).