[lkml]   [2008]   [May]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: git trees which are not yet in linux-next
On Sat, 03 May 2008 03:11:25 +0200 Stefan Richter <> wrote:

> Andrew Morton wrote:
> > git-ieee1394: git+ssh://
> 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)

<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

 \ /
  Last update: 2008-05-03 03:23    [W:0.091 / U:48.508 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site