From: Hans Reiser <reiser@namesys.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Oleg Drokin <green@namesys.com>, linux-kernel@vger.kernel.org
Subject: Re: [BK] ReiserFS changesets for 2.4 (performs writes more than 4k at a time)
Date: Tue, 10 Sep 2002 23:38:52 +0400 [thread overview]
Message-ID: <3D7E4A4C.4050104@namesys.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209101504590.16518-100000@freak.distro.conectiva
Marcelo Tosatti wrote:
>On Tue, 10 Sep 2002, Oleg Drokin wrote:
>
>
>
>>Hello!
>>
>>On Tue, Sep 10, 2002 at 11:09:38AM -0300, Marcelo Tosatti wrote:
>>
>>
>>>> This patch should only go in if 2.4.20 is 3 weeks or more away,
>>>>otherwise it should wait for the next pre1.
>>>>It passes all of our testing, but it is the kind of code that is more
>>>>likely than most to have elusive lurking bugs. It cannot be tested in
>>>>2.5 first because 2.5 is too broken at this particular moment. For the
>>>>lkml readers let me say that it also should not go onto any distros
>>>>without three weeks of testing.;-)
>>>>
>>>>
>>>So lets wait for 2.4.21pre for this one.
>>>We already have enough stuff to be tested on 2.4.20-pre for reiserfs.
>>>
>>>
>>Please pick up at least the fixes from
>>bk://thebsh.namesys.com/bk/reiser3-linux-2.4
>>I am removed everything related to reiserfs_file_write from there now, so you
>>can just do a pull.
>>
>>
>
>Huh, now that I released -pre6 _with_ this stuff by accident its too late.
>Silly me.
>
>Can you make me a tree which backouts the big write code please?
>
>Will be releasing a -pre7 shortly due to that.
>
>
>
>
>
We'll send it to you. Oleg has gone home and trying his cell phone does
not reach him, but hopefully he will read his email before bedtime.
It is not the end of the world though if this goes in.... Oleg sent it
out for testing, a user hit a bug, and then he fixed the bug and it
worked for the user. It passed testing by Oleg and Elena and some
unknown number of users on our mailing list. If you are going to
release in less than 10 days, then it needs to be yanked back out
though. If you want to yank it back out anyway, I also understand.
For now we will assume you want it out, and we'll send you the reverse
for it.
Hans
next prev parent reply other threads:[~2002-09-10 19:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 13:15 [BK] ReiserFS changesets for 2.4 (performs writes more than 4k at a time) Hans Reiser
2002-09-10 14:07 ` Dave Jones
2002-09-10 14:10 ` Oleg Drokin
2002-09-10 19:55 ` Hans Reiser
2002-09-10 14:09 ` Marcelo Tosatti
2002-09-10 15:09 ` Oleg Drokin
2002-09-10 18:16 ` Marcelo Tosatti
2002-09-10 19:38 ` Hans Reiser [this message]
2002-09-10 20:40 ` Oleg Drokin
2002-09-11 17:30 ` Arador
2002-09-11 17:39 ` Hans Reiser
2002-09-12 7:10 ` Oleg Drokin
2002-09-12 18:32 ` Arador
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=3D7E4A4C.4050104@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--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