From mboxrd@z Thu Jan  1 00:00:00 1970
From: gmate.amit@gmail.com (Kumar amit mehta)
Date: Wed, 21 Nov 2012 14:06:10 +0530
Subject: Managing linux-next tree for submitting patches
In-Reply-To: <CAHdPZaPoSQVXOFmcxp9YOmdRqyv1=GZMdEX4fyOKmSCpFPXZ-A@mail.gmail.com>
References: <20121121053634.GA2743@gmail.com>
	<CAHdPZaPT_dEpg-zDDusFYU6HFk7WJHf+bkWW=ztG90N=8fsYOA@mail.gmail.com>
	<20121121064343.GC2743@gmail.com>
	<CAHdPZaOJAQhTbw54M75hBgfxSYp+euEkg6aMnujGZUdJZoK=oQ@mail.gmail.com>
	<20121121070152.GD2743@gmail.com>
	<CAHdPZaPoSQVXOFmcxp9YOmdRqyv1=GZMdEX4fyOKmSCpFPXZ-A@mail.gmail.com>
Message-ID: <20121121083610.GE2743@gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Wed, Nov 21, 2012 at 02:47:15AM -0500, devendra.aaru wrote:
> that maintainer's tree is next tree so that next can  pickup. once the
> next pics up your changes gets merged there in next.
> 
> always its good to work against' maintainers trees, if its a fix then
> its better work on the maintainer's torvalds's tree otherwise the next
> tree in maintainer's repo
In past, I've been advised to base my work against linux-next tree.
See the mail [1] from Greg K H.

[1] http://www.spinics.net/lists/newbies/msg46076.html