All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Pysiak Satriani <pysiak.satriani@wp.pl>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: future r4 maintenance question
Date: Sat, 22 Jul 2006 12:03:28 -0600	[thread overview]
Message-ID: <44C26870.6090200@namesys.com> (raw)
In-Reply-To: <1992401892.20060722173244@wp.pl>

We are going to give changing the paradigm a try.  The difference
between 4.1-beta and 4.0 is that different plugins are the default, and
the experimental code is in the plugins you see when mounting with the
mount option 4.1-beta.   Let's see if it works in practice.....

Hans

Pysiak Satriani wrote:

>Hello,
>
>one of the concerns of LKML folks about r4 is that namesys after
>finishing their work with r4 will "rush off" to reiser5 leaving
>r4 as "stable" in a "bugfix-mode only"
>
>I understand that way of things - you don't mess with a "stable" branch
>software.
>
>But a question arises. Will namesys keep r4 in a bugfix-only mode
>(as with reiserfs v3) or will it have resources planned not only
>for bugfixes but for updates too ?
>
>I think that's a thing that needs to be very clear.
>
>Best regards,
>Maciej
>
>
>
>
>  
>


  reply	other threads:[~2006-07-22 18:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22 15:32 future r4 maintenance question Pysiak Satriani
2006-07-22 18:03 ` Hans Reiser [this message]
2006-07-22 19:51   ` Maciej Sołtysiak
2006-07-22 20:16     ` David Masover
2006-07-22 21:26       ` Maciej Sołtysiak
2006-07-23  6:23       ` Hans Reiser
2006-07-23  6:07     ` Hans Reiser
2006-07-22 18:53 ` Mike Benoit
2006-07-22 19:12   ` Matthias Barremaecker
2006-07-22 19:42   ` David Masover
2006-07-23 11:11     ` Sander Sweers
2006-07-22 20:04   ` Maciej Sołtysiak
2006-07-22 19:32 ` David Masover

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=44C26870.6090200@namesys.com \
    --to=reiser@namesys.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.