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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 May 2008 18:18:08 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux-next@...r.kernel.org, Steven French <sfrench@...ibm.com>,
	Steven Whitehouse <swhiteho@...hat.com>,
	Jeff Garzik <jeff@...zik.org>,
	Ralf Baechle <ralf@...ux-mips.org>,
	Pierre Ossman <drzeus-list@...eus.cx>, Jan Kara <jack@....cz>,
	Anton Vorontsov <cbou@...l.ru>,
	Jens Axboe <jens.axboe@...cle.com>,
	Eric Van Hensbergen <ericvh@...il.com>,
	Wim Van Sebroeck <wim@...ana.be>,
	Christian Zankel <chris@...kel.net>,
	Nicolas Pitre <nico@....org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Christoph Lameter <clameter@....com>,
	Erez Zadok <ezk@...sunysb.edu>, linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next

On Sat, 03 May 2008 03:11:25 +0200 Stefan Richter <stefanr@...6.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/