From: Oleg Drokin <green@namesys.com>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: [reiserfs-list] [BK] ReiserFS file write bug fix for 2.4
Date: Thu, 12 Sep 2002 08:53:00 +0400 [thread overview]
Message-ID: <20020912085300.A4625@namesys.com> (raw)
In-Reply-To: <200209112137.22422.Dieter.Nuetzel@hamburg.de>
Hello!
On Wed, Sep 11, 2002 at 09:37:22PM +0200, Dieter N?tzel wrote:
> > On Wed, Sep 11, 2002 at 07:34:11PM +0200, Dieter N?tzel wrote:
> > > On Wednesday 11 September 2002 19:04, Hans Reiser wrote:
> > > > Well, at least getting the new file write code into pre6 found this bug
> > > > for us.... please apply.
> > > What is the "right" way to get the new block allocation going?
> > use 2.4.19-pre2+ and it is in there ;)
> You meant 2.4.20-pre2, didn't you?
Ah, yes. 2.4.20-pre2+ of course.
Bye,
Oleg
prev parent reply other threads:[~2002-09-12 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 17:04 [BK] ReiserFS file write bug fix for 2.4 Hans Reiser
2002-09-11 17:34 ` [reiserfs-list] " Dieter Nützel
2002-09-11 17:53 ` Oleg Drokin
2002-09-11 19:37 ` Dieter Nützel
2002-09-12 4:53 ` 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=20020912085300.A4625@namesys.com \
--to=green@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
/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