From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: anything happening with kbuild 2.5?
Date: Wed, 29 May 2002 10:24:59 -0400 [thread overview]
Message-ID: <3CF4E4BB.7D475747@nortelnetworks.com> (raw)
I'm just wondering if anything is happening with kbuild 2.5, since I think it
makes sense to put it in.
There seem to be a number of fairly well known developers in favour of it
(Robert Love, Richard Gooch, Mike Fedyk, Paul Mackerras, Alan Cox, Andrea
Arcangeli, Dave Jones, for a few), and I don't see any major objections to it in
the archives.
According to my googling, the only comment Linus has had on the topic since
January is this (the typos are his):
"I'm hoping we can get there in small steps, rather than a big traumatic
merge. I'd love to just try to merge it piecemeal.
Especially as I don't find the existign system so broken."
Keith--any way you can send it in piecemeal like he wants?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2002-05-29 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 14:24 Chris Friesen [this message]
2002-05-29 15:05 ` anything happening with kbuild 2.5? Paul P Komkoff Jr
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=3CF4E4BB.7D475747@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox