linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: "HUANG Weller (CM/ESW12-CN)" <Weller.Huang@cn.bosch.com>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: F2FS still EXPERIMENTAL
Date: Mon, 14 Nov 2016 22:29:48 -0800	[thread overview]
Message-ID: <20161115062948.GA40446@jaegeuk> (raw)
In-Reply-To: <e565c64ec1e345d9ae0e507880a5f2b5@SGPMBX1004.APAC.bosch.com>

Hello,

On Tue, Nov 15, 2016 at 05:45:12AM +0000, HUANG Weller (CM/ESW12-CN) wrote:
> Hi  f2fs developers,
> 
> I am working on the kernel 3.14. I found the  F2FS still EXPERIMENTAL.
> Could you tell me from which kernel version the f2fs is stable version ?

You can pick a backported f2fs from:

http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-stable.git

> Could you let me know the roadmap about the f2fs ?

You can take a look at our development status and product information below.

https://f2fs.wiki.kernel.org/

Thanks,

> Thanks a lot.
> 
> Best regards
> 
>  Weller HUANG
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

------------------------------------------------------------------------------

  reply	other threads:[~2016-11-15  6:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  5:45 F2FS still EXPERIMENTAL HUANG Weller (CM/ESW12-CN)
2016-11-15  6:29 ` Jaegeuk Kim [this message]
2016-11-15  9:59   ` HUANG Weller (CM/ESW12-CN)
2016-11-15 18:38     ` Jaegeuk Kim
2016-11-16  1:45       ` HUANG Weller (CM/ESW12-CN)

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=20161115062948.GA40446@jaegeuk \
    --to=jaegeuk@kernel.org \
    --cc=Weller.Huang@cn.bosch.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).