From: Oleg Drokin <green@namesys.com>
To: system_lists@nullzone.org
Cc: Edward Shushkin <edward@namesys.com>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] Opss! on 2.5.6 with ReiserFS
Date: Mon, 11 Mar 2002 09:40:50 +0300 [thread overview]
Message-ID: <20020311094050.A24782@namesys.com> (raw)
In-Reply-To: <5.1.0.14.2.20020310165035.00caf5c0@192.168.2.131> <5.1.0.14.2.20020310193611.00caf1f8@192.168.2.131>
In-Reply-To: <5.1.0.14.2.20020310193611.00caf1f8@192.168.2.131>
Hello!
On Sun, Mar 10, 2002 at 07:37:22PM +0100, system_lists@nullzone.org wrote:
> I'll apply and let me inform u about result ( just like a beta-tester )
Can we also ask you to decode your oopses
(as described in /usr/src/linux/Documentation/oops-tracing.txt)
This is absolute requirement if you want unknown bugs you are hitting to
be resolved.
Luckily this bug was already known, so we was able to provide a patch
without the decoded oops, but this is not always the case.
Bye,
Oleg
prev parent reply other threads:[~2002-03-11 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 21:22 [reiserfs-list] Opss! on 2.5.6 with ReiserFS Edward Shushkin
2002-03-10 15:58 ` system_lists
2002-03-10 18:37 ` [reiserfs-list] " system_lists
2002-03-11 6:40 ` Oleg Drokin [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=20020311094050.A24782@namesys.com \
--to=green@namesys.com \
--cc=edward@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=system_lists@nullzone.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