All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: David Masover <ninja@slaphack.com>
Cc: Pysiak Satriani <pysiak.satriani@wp.pl>, reiserfs-list@namesys.com
Subject: Re: r4.1 ?
Date: Wed, 26 Jan 2005 09:44:32 -0800	[thread overview]
Message-ID: <41F7D700.9070801@namesys.com> (raw)
In-Reply-To: <41F6DC39.6000705@slaphack.com>

David Masover wrote:

>
>
> Pysiak Satriani wrote:
> | Hi,
> |
> | I was wondering how close are we to reiser4.1 ?
> | Like in % of work done or some other measure.
> |
> | http://www.namesys.com mentions r4.1
> |
> | 'this and that' will be included in r4.1
>
> Which means it would either be included in some sort of experimental
> form of r4, or (more likely, I think) in a new branch.
>
> I haven't seen any work on any of the things delayed for 4.1, meaning
> either we are 0% done, or Hans has moved to a cathedral style of
> development.
>
> That, or I just haven't noticed such work.  I don't often read source 
> code.
>
It is an interesting question whether with a plugin architectural model 
we perhaps need a fundamentally different software release model, with 
the technical design now controlling what is the optimal release model.

There are three big things in progress right now that are alpha or worse 
quality.

Compression, Viewprinting (www.namesys.com/blackbox_security.html), and 
sys_reiser4()'s semantic enhancements.  Compression will hopefully be 
ready first.  Compression will have enough performance impact to justify 
calling it a 4.1 release and doing a press release, but you understand 
that in reality it is just a plugin.....

      reply	other threads:[~2005-01-26 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 21:44 r4.1 ? Pysiak Satriani
2005-01-25 23:54 ` David Masover
2005-01-26 17:44   ` 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=41F7D700.9070801@namesys.com \
    --to=reiser@namesys.com \
    --cc=ninja@slaphack.com \
    --cc=pysiak.satriani@wp.pl \
    --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.