From: Keith Owens <kaos@ocs.com.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Converting the 2.5 kernel to kbuild 2.5
Date: Fri, 07 Dec 2001 19:29:18 +1100 [thread overview]
Message-ID: <26499.1007713758@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 06 Dec 2001 21:10:11 -0800." <Pine.LNX.4.33.0112062109400.7866-100000@penguin.transmeta.com>
On Thu, 6 Dec 2001 21:10:11 -0800 (PST),
Linus Torvalds <torvalds@transmeta.com> wrote:
>
>On Fri, 7 Dec 2001, Keith Owens wrote:
>>
>> Linus, the time has come to convert the 2.5 kernel to kbuild 2.5.
>
>We're getting the block IO layer in shape first, the time has not come for
>_anything_ else before that.
That is what I said ....
2.5.1 Semi-stable kernel, after bio is working.
2.5.2-pre1 Add the kbuild 2.5 and CML2 code, still using
Makefile-2.5, supporting both CML1 and CML2.
2.5.2-pre2 Remove kbuild 2.4 code, rename Makefile-2.5 to Makefile.
Still supporting both CML1 and CML2.
2.5.2-pre3 Remove CML1 support.
Is that timetable acceptable?
next prev parent reply other threads:[~2001-12-07 8:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 4:17 Keith Owens
2001-12-07 4:30 ` [kbuild-devel] (no subject) Tom Rini
2001-12-07 4:36 ` Keith Owens
2001-12-07 4:41 ` Tom Rini
2001-12-07 11:01 ` Russell King
2001-12-07 11:07 ` Keith Owens
2001-12-07 5:10 ` your mail Linus Torvalds
2001-12-07 5:12 ` [kbuild-devel] " Eric S. Raymond
2001-12-07 8:29 ` Keith Owens [this message]
2001-12-27 18:09 ` Andre Hedrick
2001-12-27 18:55 ` Linus Torvalds
2001-12-27 19:41 ` Andrew Morton
2001-12-28 22:14 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2001-12-04 17:03 [kbuild-devel] Converting the 2.5 kernel to kbuild 2.5 Eric S. Raymond
2001-12-04 17:44 ` Alan Cox
2001-12-05 1:59 ` Cameron Simpson
2001-12-05 8:29 ` Eric S. Raymond
2001-12-03 1:06 Keith Owens
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=26499.1007713758@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.