All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Info <info@acculin.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Impressed. Any info other than source?
Date: Tue, 01 Feb 2005 08:27:01 -0800	[thread overview]
Message-ID: <41FFADD5.7010605@namesys.com> (raw)
In-Reply-To: <1107223140.28831.110.camel@cunegonde.paulshome.acculin.com>

Info wrote:

>Hello,
>
>I am really impressed by what you're doing with Reiserfs.
>It is a wonderful mix of the immediately usable and great
>promise for the future. 
>
>I am somewhat amazed that this is such a low traffic list.
>Am I missing some other place where this stuff is discussed?
>  
>
Not really.  We are in a period of stabilizing rather than designing new 
stuff.  Unfortunately, one always spends far more time stabilizing than 
designing.....

>Quoting from your website:
>  
>
>>Looking at the coin from the other side, we want to make
>>it an order of magnitude less work to add features to 
>>ReiserFS so that both users and Namesys can add at least 
>>an order of magnitude more of them.
>>    
>>
>
>To this end is there any documentation between the general 
>descriptions (.../v4/v4.html and .../whitepaper.html) and
>the actual source code? I have searched your site and the
>web (although I haven't tried BitKeeper yet) and can't find
>anything. It is not the actual internal workings so much as
>how to modify a plugin that I'm interested in. Any sort of
>howto type documentation?
>  
>
The source code is intended to be very readable.  I don't think there 
should be any documentation besides web site and source code.

>Any URLs gratefully received!
>
>Regards,
>Paul Hilton
>
>
>
>  
>


  reply	other threads:[~2005-02-01 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  1:59 Impressed. Any info other than source? Info
2005-02-01 16:27 ` Hans Reiser [this message]
2005-02-02  1:16   ` David Masover
2005-02-02 16:05   ` Dr. Giovanni A. Orlando

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=41FFADD5.7010605@namesys.com \
    --to=reiser@namesys.com \
    --cc=info@acculin.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.