From: Hans Reiser <reiser@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Hans Reiser <reiser@bitshadow.namesys.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [BK] [PATCH] reiserfs changeset 7 of 7 to include into 2.4 tree
Date: Mon, 12 Aug 2002 00:40:21 +0400 [thread overview]
Message-ID: <3D56CBB5.3010905@namesys.com> (raw)
In-Reply-To: 3D56C6A4.5010604@namesys.com
Hans Reiser wrote:
> Alan Cox wrote:
>
>> On Fri, 2002-08-09 at 18:38, Christoph Hellwig wrote:
>>
>>
>>> Are you sure you want to have a new block allocator in the stable
>>> series
>>> before it has been added to 2.5?
>>>
>>
>>
>> Thats what I was also wondering. It seems like its an experimental
>> update rather than a bug fix so ought to be 2.5 stuff
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
>>
> The non-default mount options are experimental, and the options to
> have things revert to old behaviour play it safe just in case.
>
> I understand why all of you are doubtful about it going into 2.4, it
> is not that you are crazy, but my closeness to the code makes me think
> it is stable enough that it should go in. Also remember that we have
> an extensive test suite, we have been benchmarking variations on this
> code for months, and I frankly don't think that 2.5 insertion will get
> it enough testing to be instructive to us.
>
I meant to add that the default mount options are not experimental in my
view, they are tested and chosen as what works well and is simple/elegant.
--
Hans
next prev parent reply other threads:[~2002-08-11 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 16:36 [BK] [PATCH] reiserfs changeset 7 of 7 to include into 2.4 tree Hans Reiser
2002-08-09 17:38 ` Christoph Hellwig
2002-08-11 20:21 ` Alan Cox
2002-08-11 20:18 ` Hans Reiser
2002-08-11 20:40 ` Hans Reiser [this message]
2002-08-09 20:52 ` Andrew Morton
2002-08-10 17:55 ` Hans Reiser
2002-08-10 18:14 ` Hans Reiser
2002-08-12 18:36 ` Marcelo Tosatti
2002-08-12 20:01 ` Hans Reiser
2002-08-12 20:33 ` 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=3D56CBB5.3010905@namesys.com \
--to=reiser@namesys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiser@bitshadow.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