From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [kbuild-devel] (no subject)
Date: Fri, 07 Dec 2001 15:36:13 +1100 [thread overview]
Message-ID: <24800.1007699773@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 06 Dec 2001 21:30:59 PDT." <20011207043059.GI30935@cpe-24-221-152-185.az.sprintbbd.net>
On Thu, 6 Dec 2001 21:30:59 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>On Fri, Dec 07, 2001 at 03:17:53PM +1100, Keith Owens wrote:
>> 2.5.2-pre1 Add the kbuild 2.5 and CML2 code, still using
>> Makefile-2.5, supporting both CML1 and CML2.
>> i386, sparc, sparc64 can use either kbuild 2.4 or 2.5,
>> 2.5 is recommended.
>> ia64 can only use kbuild 2.5.
>> Other architectures continue to use kbuild 2.4.
>> Wait 24 hours for any major problems then -
>
>Could we wait longer here? Maybe 48 or 72 to give other arches time to
>convert and attempt to sync again? Or at least show it to Keith so he
>can try and sync it up. :)
We will not get all architectures converted in 48 hours or even 72.
kbuild 2.5 has been available for months and only i386, ia64, sparc32
(I did all those) and sparc64 (Ben Collins) have been converted. Alpha
is in progress. Unconverted architectures stay on 2.5.2-pre1 until
they do the conversion, but there is no need to hold up everybody else.
next prev parent reply other threads:[~2001-12-07 4:36 UTC|newest]
Thread overview: 13+ 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 [this message]
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 ` Converting the 2.5 kernel to kbuild 2.5 Keith Owens
2001-12-27 18:09 ` your mail Andre Hedrick
2001-12-27 18:55 ` Linus Torvalds
2001-12-27 19:41 ` Andrew Morton
2001-12-28 22:14 ` Martin Dalecki
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=24800.1007699773@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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 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.