From: Martin Dalecki <dalecki@evision-ventures.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: PROBLEM: Kernel Panic on 2.5.6 and 2.5.7-pre1 boot [PATCH] and discussion of Linux testing procedures
Date: Wed, 13 Mar 2002 14:57:23 +0100 [thread overview]
Message-ID: <3C8F5AC3.6040904@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0203131048490.2181-100000@imladris.surriel.com>
Rik van Riel wrote:
> On Wed, 13 Mar 2002, Hans Reiser wrote:
>
>
>>I would encourage requiring that every patch sent to Linus have two
>>signatures on it, one indicating that the author has tested it and
>>another indicating what second person has tested it.
>>
>
> Agreed. Linus and Marcelo are very busy and shouldn't be
> bothered with untested patches. If we only send them
> known-good stuff their lives should get a little bit
> easier.
You don't understand by accident that sometimes blind untested
changes serve the purpose of hinting at API changes in
areas where once doesn't have the slightest opportunity
of testing? Just simple count how many FS there are out there
and you should see that there is no chance for "quality"
testing before submission of advancements there.
Breakage is the price you have to pay for advancements.
(I'm not arguing over the particular case in quesiton here.
I'm just arguing over the proposal.)
next prev parent reply other threads:[~2002-03-13 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 10:02 PROBLEM: Kernel Panic on 2.5.6 and 2.5.7-pre1 boot [PATCH] and discussion of Linux testing procedures Hans Reiser
2002-03-13 13:50 ` Rik van Riel
2002-03-13 13:57 ` Martin Dalecki [this message]
2002-03-13 14:09 ` Alexander Viro
2002-03-13 14:18 ` Martin Dalecki
2002-03-13 17:03 ` [reiserfs-list] " Valdis.Kletnieks
2002-03-13 17:44 ` Alexander Viro
2002-03-13 18:46 ` Hans Reiser
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=3C8F5AC3.6040904@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=riel@conectiva.com.br \
/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