From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: "Robin H. Johnson" <robbat2@orbis-terrarum.net>,
reiserfs-list@namesys.com
Subject: Re: possible bug - fsck shows perfect results, linux refuses to mount
Date: Mon, 31 Mar 2003 20:03:20 +0400 [thread overview]
Message-ID: <3E8866C8.5080007@namesys.com> (raw)
In-Reply-To: <20030331120014.C25533@namesys.com>
Oleg Drokin wrote:
>
>
>>A question for you, so I can support things. Is there a list somewhere
>>of features requested, and how much you money you want to be paid to add
>>them in? Especially the smaller features (hint hint).
>>
>>
>
>Well, there is http://namesys.com/support.html , as of features, usually
>we expect customers to come up with features they need. If you lack something
>in reiserfs and you are willing to pay, we can implement it.
>If you are happy with the current features-set, why to pay for features that
>would be never used?
>
>Bye,
> Oleg
>
>
>
>
This was the wrong answer.;-)
There are lots of features needed but not implemented. You could
sponsor our integrating support for badblock handling to the current
reiser3 and reiser4 for $1000.
--
Hans
prev parent reply other threads:[~2003-03-31 16:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 7:22 possible bug - fsck shows perfect results, linux refuses to mount Robin H. Johnson
2003-03-31 7:34 ` Oleg Drokin
2003-03-31 7:49 ` Robin H. Johnson
2003-03-31 8:00 ` Oleg Drokin
2003-03-31 8:34 ` Soeren Sonnenburg
2003-03-31 8:41 ` Oleg Drokin
2003-03-31 8:48 ` Soeren Sonnenburg
2003-03-31 9:02 ` Oleg Drokin
2003-03-31 8:37 ` Robin H. Johnson
2003-03-31 8:56 ` Oleg Drokin
2003-03-31 9:16 ` Robin H. Johnson
2003-03-31 9:24 ` Oleg Drokin
2003-03-31 10:17 ` Robin H. Johnson
2003-03-31 10:36 ` Oleg Drokin
2003-03-31 11:13 ` Robin H. Johnson
2003-03-31 11:33 ` Oleg Drokin
2003-03-31 13:57 ` Oleg Drokin
2003-03-31 16:03 ` Hans Reiser [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=3E8866C8.5080007@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=robbat2@orbis-terrarum.net \
/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.