Re: git trees which are not yet in linux-next

[Andrew Morton <akpm@linux-foundation.org>]

On Sat, 03 May 2008 03:11:25 +0200 Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> Andrew Morton wrote:
> > git-ieee1394: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git#for-mm
> 
> Stephen pulls linux1394-2.6.git#for-next.
> 
> > Guys, could you please prepare a tree for Stephen and send the details
> > over to him?  Please Cc me also.
> > 
> > Once this has happened, there should be no need to run a separate for-mm
> > branch.  I'll just switch over to using whatever branch linux-next is
> > using.
> 
> -mm is going to become identical in content to -next?

-mm will be (and now is)

origin.patch
linux-next.patch
<other patches>

Where "other patches" includes git trees which aren't in linux-next.

So yes, you should drop #for-mm and add #for-next.

I will pull your #for-next brach daily, but I'll only include it (as
git-ieee1394.patch) if for some reason linux-next.patch needed to be
dropped.