From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Rik van Riel <riel@conectiva.com.br>,
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 15:18:05 +0100 [thread overview]
Message-ID: <3C8F5F9D.6050600@evision-ventures.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0203130903470.22930-100000@weyl.math.psu.edu>
Alexander Viro wrote:
> Proposal is a bit naive, though - in most of the cases fuckups merrily
> pass original testing.
No argument here - this was my point.
next prev parent reply other threads:[~2002-03-13 14:20 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
2002-03-13 14:09 ` Alexander Viro
2002-03-13 14:18 ` Martin Dalecki [this message]
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=3C8F5F9D.6050600@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 \
--cc=viro@math.psu.edu \
/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