Message-Id: <20121127094818.c2fa217b785ba4cb386bfe16@canb.auug.org.au>
Date:	Tue, 27 Nov 2012 09:48:18 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	jaegeuk.kim@...sung.com
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	gregkh@...uxfoundation.org, viro@...iv.linux.org.uk, arnd@...db.de,
	tytso@....edu, chur.lee@...sung.com, cm224.lee@...sung.com,
	jooyoung.hwang@...sung.com
Subject: Re: [RESEND] Request f2fs filesystem inclusion in linux-next

Hi,

On Mon, 26 Nov 2012 20:37:40 +0900 Jaegeuk Kim <jaegeuk.kim@...sung.com> wrote:
>
> 2012-11-26 (월), 10:18 +1100, Stephen Rothwell:
> > 
> > On Sat, 24 Nov 2012 14:28:45 +0900 Jaegeuk Kim <jaegeuk.kim@...sung.com> wrote:
> > >
> > > About two month ago, I submitted a new file system, namely
> > > flash-friendly file system (f2fs) to LKML.
> > >  http://en.wikipedia.org/wiki/F2FS
> > >  http://lkml.org/lkml/2012/10/5/205
> > >  http://lwn.net/Articles/518718/
> > > 
> > > In the mean time, many folks have pointed out several essential issues
> > > on f2fs, and now I think most of them have been resolved moderately.
> > > 
> > > So, I'd like to request a new branch being included in linux-next for
> > > the purpose of merging into the next mainline kernel.
> > 
> > I have no problem adding this to linux-next (and noone has screamed aver
> > the past few days, so that is a good sign) except that the branch you
> > have submitted is actually based on linux-next itself.  You cannot base
> > anything on linux-next as it rebases every day.  You need to base your
> > tree in Linus' tree (or some other *stable* tree).
> 
> I've done making a correct tree.
> Could you please merge the following f2fs patches?
> 
> 1. tree
> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
> 
> 2. branch
> dev
> 
> 3. Contact
> Jaegeuk Kim <jaegeuk.kim@...sung.com>

OK, that looks much better.  Added from today.  In case you are not
aware, I will attempt to refetch that branch every morning before I start
merging the bits of linux-next together.  So any changes you make to that
branch should be reflected in the next linux-next release.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@...b.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists