From: Paul Dickson <paul@permanentmail.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: klibc - another libc?
Date: Mon, 12 Jun 2006 19:31:19 -0700 [thread overview]
Message-ID: <20060612193119.e0ff94d8.paul@permanentmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606100257550.17704@scrub.home>
On Sat, 10 Jun 2006 03:15:59 +0200 (CEST), Roman Zippel wrote:
> On Fri, 9 Jun 2006, H. Peter Anvin wrote:
>
> > > If you wouldn't remove all old init code at once it would still be
> > > possible to build a kernel this way. Why are you making it mandatory? Why
> > > don't you leave it optional for a while and only gradually remove the old
> > > code? This way distributions/users can experiment with it regarding their
> > > current initrd/boot setups.
> >
> > Linus vetoed that option years ago.
>
> Name dropping is of course always impressive - scares little kids and all.
> Could you please provide more info, what exactly he vetoed?
His rule was no code was to be added to the kernel code unless it already
had a user. So there would be no adding code hoping a user would appear.
If I'm wrong, I'll likely be corrected... :-)
-Paul
prev parent reply other threads:[~2006-06-13 2:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 8:51 Michael Tokarev
2006-06-07 21:17 ` H. Peter Anvin
2006-06-07 22:42 ` Roman Zippel
2006-06-08 15:32 ` H. Peter Anvin
2006-06-09 14:13 ` Roman Zippel
2006-06-09 19:02 ` H. Peter Anvin
2006-06-09 19:13 ` Michael Tokarev
2006-06-09 19:29 ` H. Peter Anvin
2006-06-10 1:28 ` Roman Zippel
2006-06-10 16:24 ` Michael Tokarev
2006-06-10 17:28 ` Sam Ravnborg
2006-06-11 0:21 ` Roman Zippel
2006-06-10 1:15 ` Roman Zippel
2006-06-10 6:13 ` Sam Ravnborg
2006-06-10 23:37 ` Roman Zippel
2006-06-13 2:31 ` Paul Dickson [this message]
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=20060612193119.e0ff94d8.paul@permanentmail.com \
--to=paul@permanentmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
Powered by JetHome