From: Hans Reiser <reiser@namesys.com>
To: Jonathan Briggs <jbriggs@esoft.com>
Cc: reiserfs-list@namesys.com
Subject: Re: State of the Reiser4 FS
Date: Wed, 15 Mar 2006 12:43:57 -0800 [thread overview]
Message-ID: <44187C8D.5050105@namesys.com> (raw)
In-Reply-To: <1142451941.16641.32.camel@localhost>
Jonathan Briggs wrote:
>On Tue, 2006-03-14 at 23:14 -0800, Hans Reiser wrote:
>[snip]
>
>
>>They claim that if we don't use the ext3 code
>>in our fs then they will be forced to shoulder an extra burden to
>>maintain our code. We are not allowed to specify that they should not
>>maintain our code at all. I need to read more Kafka I think, it is hard
>>for me to understand it all.
>>
>>
>
>Err, this actually does make a lot of sense Hans.
>
>The mainline Linux Kernel code is maintained by everyone that can
>convince Linus or a sub-maintainer to accept their patch. In order to
>
>
I am the reiserfs/reiser4 sub-maintainer. So, if reiser4 works well,
and is faster than any other Linux FS, and it is, maintaining it over
time is for me to worry about, not them.
next prev parent reply other threads:[~2006-03-15 20:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 10:41 State of the Reiser4 FS Avuton Olrich
2006-03-14 11:45 ` Vladimir V. Saveliev
2006-03-14 15:32 ` Clemens Eisserer
2006-03-15 7:14 ` Hans Reiser
2006-03-15 8:57 ` Andreas Schäfer
2006-03-15 18:29 ` Hans Reiser
2006-03-15 19:27 ` Andreas Schäfer
2006-03-15 21:08 ` Andreas Dilger
2006-03-16 0:58 ` 4k at a time only works well for an OS that does less per iteration than Linux does Hans Reiser
2006-03-15 19:45 ` State of the Reiser4 FS Jonathan Briggs
2006-03-15 20:43 ` Hans Reiser [this message]
2006-03-15 21:25 ` Andreas Schäfer
2006-03-15 8:45 ` Hans Reiser
2006-03-15 12:59 ` Avuton Olrich
2006-03-15 18:33 ` Hans Reiser
2006-03-26 11:27 ` 2.6.16 patch jp
2006-03-27 17:27 ` jp
2006-03-28 11:42 ` Vladimir V. Saveliev
2006-03-28 12:54 ` Tassilo Horn
2006-03-28 17:12 ` Danny Milosavljevic
2006-03-28 18:00 ` Tassilo Horn
2006-03-28 23:22 ` Jake Maciejewski
2006-03-27 20:10 ` Marcus Furlong
2006-03-27 19:44 ` Tassilo Horn
2006-03-27 21:32 ` Marcus Furlong
2006-03-27 20:41 ` Tassilo Horn
2006-03-27 21:29 ` Tassilo Horn
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=44187C8D.5050105@namesys.com \
--to=reiser@namesys.com \
--cc=jbriggs@esoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.