Based on the discussion to date, here is a draft transition plan. Please
read it to make sure it is representing reality correctly.
mec, please take this and edit as necessary to fill in the remaining blanks.
Your call when we release it.
(If I missed the name of anyone on the team, apologies.)
Michael Elizabeth Chastain <[EMAIL PROTECTED]>:
> > Transition patch 1: CML2 installation
> > Transition patch 2: Kaos makefiles installation
>
> Yeah. Now you can send mega-patches to Linus and tell him that
> he won't get caught in dualling mega-patches because the devel list
> has approved th
There's going to have to be at least one CML2 patch after Kaos makefiles go in.
That's to change the output of configtrans.py from CML1 format
# FOO is not set
to CML2 format
FOO=n
so don't-cares can be passed around in partial configurations.
So I'm seeing four steps now:
1. CML2 installat
> Transition patch 1: CML2 installation
> Transition patch 2: Kaos makefiles installation
Yeah. Now you can send mega-patches to Linus and tell him that
he won't get caught in dualling mega-patches because the devel list
has approved this road map.
> However, the roadmap document needs to be mo
Michael Elizabeth Chastain <[EMAIL PROTECTED]>:
> Okay, then here is my proposal for a roadmap:
>
> . cml2 goes first
>
> . kaos makefiles go in after cml2.
> they don't have to work with cml1 unless keith wants them to.
>
> All in favor, say "aye".
Aye. Good, this is a start.
Transition
Keith Owens <[EMAIL PROTECTED]>:
> Everybody patching the same menu does not work, it guarantees patch
> failures. There is some code around that build up menus from
> fragments, but it only works for menus and requires special code in
> everything that reads the files, because the result must be
On Mon, 25 Jun 2001 08:43:57 -0700,
Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote:
>Keith writes:
>> Yes there is. Eric is ready, I am not quite ready yet, I am still
>> fighting implicit dependencies. ESR goes first.
>
>Okay, then here is my proposal for a roadmap:
>
>. cml2 goes first
Keith writes:
> Yes there is. Eric is ready, I am not quite ready yet, I am still
> fighting implicit dependencies. ESR goes first.
Okay, then here is my proposal for a roadmap:
. cml2 goes first
. kaos makefiles go in after cml2.
they don't have to work with cml1 unless keith wants them to
On Mon, 25 Jun 2001 08:06:11 -0700,
Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote:
>Oof, both of you want to go first, and there are no "killer arguments"
>for which to prefer.
Yes there is. Eric is ready, I am not quite ready yet, I am still
fighting implicit dependencies. ESR goes fir
Michael Elizabeth Chastain <[EMAIL PROTECTED]>:
> Oof, both of you want to go first, and there are no "killer arguments"
> for which to prefer.
Then flip a coin. Seriously. I'll accept your call.
> esr> Fundamentally CML2 doesn't care where the input and output lives.
> esr> Input and output l
Oof, both of you want to go first, and there are no "killer arguments"
for which to prefer.
esr> Fundamentally CML2 doesn't care where the input and output lives.
esr> Input and output locations are specifiable on the command line with
esr> defaults to the current directory.
Keith, is this every
On Mon, 25 Jun 2001 07:35:05 -0700,
Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote:
>Actually I think of myself as more "emeritus" than "honcho".
>
>My ideas for a roadmap:
>
>. pick one patch to go first rather than put both in the same point
> release.
I was thinking of kbuild 2.5 with
Michael Elizabeth Chastain <[EMAIL PROTECTED]>:
> My ideas for a roadmap:
>
> . pick one patch to go first rather than put both in the same point
> release.
I think that might reduce the coordination problems, yes.
> . i favor doing cml2 first, because kaos makefiles depend on the cml.
I di
Actually I think of myself as more "emeritus" than "honcho".
My ideas for a roadmap:
. pick one patch to go first rather than put both in the same point
release.
. i favor doing cml2 first, because kaos makefiles depend on the cml.
. kaos makefiles have separate source and target trees. it
I'm validating the address to my patch for 2.2.19. Yeah, I know it works,
but it's so easy to test.
Michael
diff -u -r -N linux-2.2.19/MAINTAINERS linux/MAINTAINERS
--- linux-2.2.19/MAINTAINERSSun Mar 25 11:37:29 2001
+++ linux/MAINTAINERS Sat Jun 23 20:04:21 2001
@@ -211,7 +211,8 @@
CON
15 matches
Mail list logo
