linux-kernel - 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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080502151206.b40f77ea.akpm@linux-foundation.org>
Date:	Fri, 2 May 2008 15:12:06 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	linux-next@...r.kernel.org
Cc:	Steven French <sfrench@...ibm.com>,
	Steven Whitehouse <swhiteho@...hat.com>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	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: git trees which are not yet in linux-next


git-cifs: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/sfrench/cifs-2.6.git

git-gfs2-nmw: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-nmw.git

git-ieee1394: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git#for-mm

git-jg-misc: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git#irq-remove

git-libata-all: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-2.6.git

git-mips: git://git.linux-mips.org/pub/scm/upstream-akpm.git#mips-for-mm

git-mmc: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git#for-andrew

git-udf: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/jack/linux-udf-2.6.git#for_mm

git-battery: git://git.infradead.org/battery-2.6.git

git-block: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git#for-akpm

git-v9fs: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git#v9fs-devel

git-watchdog: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/wim/linux-2.6-watchdog-mm.git

git-xtensa: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/czankel/xtensa-2.6.git#testing

git-orion: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/nico/orion.git

git-pekka: git+ssh://master.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6.git#for-mm


(This list is probably incomplete - there might be other trees which are
presently empty but which aren't in linux-next yet)

(Jeff, git-libata-all is a pretty important one)

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.

I'll continue to pull all the git trees, although I'll expect to drop them
again.  I will do this to keep my list of git URLs fresh.  So if for some
reason linux-next isn't getting updated I can drop it and switch back to
the individual git trees.


I don't yet know how I'll get along basing -mm on linux-next.  The first
problem is working out "how the heck did that patch get into linux-next"? 
That would be much easier if the signoff trail was complete for git-based
patches, but it often is not.

Thanks.

(git-unionfs and such things will remain -mm-only)
--
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/