From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.16
Date: 27 Nov 2001 00:08:29 -0800 [thread overview]
Message-ID: <9tvhlt$g5j$1@cesium.transmeta.com> (raw)
In-Reply-To: <20011127083530.A13584@bee.lk> <Pine.LNX.4.33L.0111270551210.4079-100000@imladris.surriel.com> <20011127135847.A22859@bee.lk>
Followup to: <20011127135847.A22859@bee.lk>
By author: Anuradha Ratnaweera <anuradha@gnu.org>
In newsgroup: linux.dev.kernel
>
> It is still not okey to include even _small_ changes, because it is hard to
> define what small is. Although we are sure that is is going to break,
> Murphey's laws may get in ...;)
>
> So better have a _policy_ of not doing so.
>
Sorry, but you have just crossed the line of what is reasonable to
demand of other people. If you don't trust the maintainers and want
to maintain such a policy, fork the kernel and start maintaining it
yourself.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-11-27 8:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 12:30 Linux 2.4.16 Marcelo Tosatti
2001-11-26 14:31 ` Firewire hotplug Samuel Maftoul
2001-11-26 15:58 ` William Stearns
2001-11-26 16:55 ` Linux 2.4.16 Dominik Kubla
2001-11-27 2:35 ` Anuradha Ratnaweera
2001-11-27 2:44 ` Jeff Garzik
2001-11-27 2:56 ` Anuradha Ratnaweera
2001-11-27 9:57 ` Helge Hafting
2001-11-27 7:51 ` Rik van Riel
2001-11-27 7:58 ` Anuradha Ratnaweera
2001-11-27 8:08 ` H. Peter Anvin [this message]
2001-11-27 8:26 ` Andreas Jaeger
2001-11-27 8:45 ` Anuradha Ratnaweera
2001-11-27 10:00 ` Alan Cox
2001-11-28 13:38 ` Marcelo Tosatti
2001-11-29 2:44 ` Anuradha Ratnaweera
2001-11-29 3:08 ` Rik van Riel
2001-11-29 4:09 ` Mike Fedyk
2001-11-29 12:38 ` Horst von Brand
2001-11-29 13:50 ` Rik van Riel
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='9tvhlt$g5j$1@cesium.transmeta.com' \
--to=hpa@zytor.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 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.