Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org
Subject: Re: Nilfs merged in mainline
Date: Wed, 08 Apr 2009 14:54:10 +0900 (JST)	[thread overview]
Message-ID: <20090408.145410.88470856.ryusuke@osrg.net> (raw)
In-Reply-To: <49DC2348.8040208-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>

Hi,
On Wed, 08 Apr 2009 06:08:40 +0200, David Arendt <admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org> wrote:
> Hi,
> 
> Congratulations
> 
> Is the in kernel nilfs equivalent to the latest released one with data 
> corruption bugs fixed, or is it some earlier version ?

It's a little earlier version.
I'll send the missed recent bug-fixes to Linus as soon as possible.

Regards,
Ryusuke
 
> Bye,
> David Arendt
> 
> Ryusuke Konishi wrote:
> > Hi everyone,
> >
> > Just a quick note to let you know that Linus merged nilfs2 in his
> > mainline kernel (2.6.30-rc1).
> >
> > Though still we should stay sharp until 2.6.30 will be released
> > formally, I'd like to thank to everyone who contributed to the code,
> > tested, commented, sent us bug reports, and so forth.
> >
> > I'm backlogged on several bug-fixes and many todo items, so it's just
> > a pass point.  We look forward to everyone's continued cooperation.
> >
> > Cheers,
> > Ryusuke

      parent reply	other threads:[~2009-04-08  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  3:03 Nilfs merged in mainline Ryusuke Konishi
     [not found] ` <20090408.120329.88469835.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-04-08  3:57   ` Alex Bitney
2009-04-08  4:08   ` David Arendt
     [not found]     ` <49DC2348.8040208-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2009-04-08  5:54       ` Ryusuke Konishi [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=20090408.145410.88470856.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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