public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lyamin <flx@msu.ru>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Kobajashi Zaghi <kobajashi@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re:  The Future of ReiserFS development
Date: Wed, 11 Oct 2006 20:41:03 +0400	[thread overview]
Message-ID: <20061011164103.GA1470@alias.nmd.msu.ru> (raw)
In-Reply-To: <Pine.LNX.4.61.0610111319490.26779@yvahk01.tjqt.qr>


Well, this is correct statement if we are talking about 3.6, its only bugfixes
lately. Altough SuSE people used to add some new stuff
like ACL support.

As for reiser4, we are still going through  revision, thanks to AKPM. Chunking
out patches,fixing issues and generally cleaning the house.

Yes, we are rather shaked and stressed at moment, altough I can not say, we
didn't  seen it coming.
I, personally, really like how US police acted exactly like their russian
counterpart:  e.g. sitting on their ass for whole month, waiting,  so they can
declare person officially missing and then just press charges against whoever
looks most vulnerable. Well, probably I am wrong. Time will show.


What WE (e.g. reiser4 dev people) are planng to do ?

Short term ( present +  6 months ):
We will just buzz along as ussual, chunking out patches and going through
review, while pursuing existing business oportunities to get some funding.

Long term (6 months from now  and beyond):
If it goes way we hope it will go. Well... We will do fine.
If it goes bad. That is where it becomes tricky. We will try to appoint a proxy
to run Namesys business.


Thats it for now.



Wed, Oct 11, 2006 at 01:20:39PM +0200, Jan Engelhardt wrote:
> 
> > What is the plan? Could i
> > migrate from reiserfs to another journaling filesystem? How will this
> > trouble affect reiserfs development?
> 
> Since development has pretty much ceased already, there is nothing to 
> lose if you continue to use reiserfs.
> 
> 
> 	-`J'
> -- 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
"the liberation loophole will make it clear.."
lex lyamin

  reply	other threads:[~2006-10-11 16:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11  8:53 The Future of ReiserFS development Kobajashi Zaghi
2006-10-11  8:55 ` Ralf Hildebrandt
2006-10-11 11:20 ` Jan Engelhardt
2006-10-11 16:41   ` Alexander Lyamin [this message]
     [not found]   ` <80294dc60610110937g44164a77nb2742f8a2f121574@mail.gmail.com>
2006-10-11 19:37     ` Jan Engelhardt
2006-10-11 16:44 ` David Schwartz
2006-10-11 17:00   ` Mike Fowler
2006-10-11 17:56 ` Alan Cox
2006-10-11 18:56 ` Luigi Genoni
  -- strict thread matches above, loose matches on Subject: below --
2006-10-12  8:36 roland
2006-10-12 14:13 ` Jörn Engel
2006-10-12 14:19 ` Jan Engelhardt
2006-10-12 15:03 ` Lee Revell
2006-10-12 15:17 Online Journaled File System

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=20061011164103.GA1470@alias.nmd.msu.ru \
    --to=flx@msu.ru \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kobajashi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox