From: Andreas Jaeger <aj@suse.de>
To: Anuradha Ratnaweera <anuradha@gnu.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.16
Date: Tue, 27 Nov 2001 09:26:20 +0100 [thread overview]
Message-ID: <ho1yik39hv.fsf@gee.suse.de> (raw)
In-Reply-To: <20011127083530.A13584@bee.lk> <Pine.LNX.4.33L.0111270551210.4079-100000@imladris.surriel.com> <20011127135847.A22859@bee.lk>
In-Reply-To: <20011127135847.A22859@bee.lk> (Anuradha Ratnaweera's message of "Tue, 27 Nov 2001 13:58:47 +0600")
Anuradha Ratnaweera <anuradha@gnu.org> writes:
> On Tue, Nov 27, 2001 at 05:51:59AM -0200, Rik van Riel wrote:
>> On Tue, 27 Nov 2001, Anuradha Ratnaweera wrote:
>> > On Mon, Nov 26, 2001 at 10:30:08AM -0200, Marcelo Tosatti wrote:
>> > >
>> > > final:
>> > > - Fix 8139too oops (Philipp Matthias Hahn)
>> >
>> > Won't that be a good idea to keep the -final the same as the last -pre?
>>
>> That's basically what happened. This 8139too fix is
>> ONE LINE, in a self-contained piece of code.
>
> 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 ...;)
It's Marcelo deciding what it's ok and what not. He's the one
responsible for it. If you like to give him a friendly advise - fine
with me but I don't think you've got the right to *define* what's ok
and what not for Marcelo.
I've got the impression from these threads about maintaince on lkml
that a number of people try to force something on Marcelo without
giving him a chance to find his own way of doing it. I trust Marcelo
that he'll do the right thing.
Could we get back to coding and testing?
Andreas
P.S. I trimmed the CC list to only include lkml.
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-11-27 8:26 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
2001-11-27 8:26 ` Andreas Jaeger [this message]
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=ho1yik39hv.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=anuradha@gnu.org \
--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