From: Lukasz Trabinski <lukasz@wsisiz.edu.pl>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops on 2.4.22-pre2
Date: Wed, 9 Jul 2003 00:20:21 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.53.0307090014290.26653@oceanic.wsisiz.edu.pl> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307081828020.25622@freak.distro.conectiva>
On Tue, 8 Jul 2003, Marcelo Tosatti wrote:
Hello.
> We have discussed the problem and there is a partial fix in the current
> 2.4 BK tree. ChangeSet@1.1070 is the fix.
Great.
> Can you try to reproduce the problem with the latest BK tree?
I will try, but probably, it can be difficulty to reproduce, because it
was happaned only once.
--
*[ Łukasz Trąbiński ]*
SysAdmin @wsisiz.edu.pl
next prev parent reply other threads:[~2003-07-08 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 13:36 Oops on 2.4.22-pre2 Lukasz Trabinski
2003-07-08 21:31 ` Marcelo Tosatti
2003-07-08 22:20 ` Lukasz Trabinski [this message]
2003-07-09 1:30 ` Marcelo Tosatti
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=Pine.LNX.4.53.0307090014290.26653@oceanic.wsisiz.edu.pl \
--to=lukasz@wsisiz.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@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;
as well as URLs for NNTP newsgroup(s).