Home » Mailing list archives » linux-kernel » 2008 » May » 2

git trees which are not yet in linux-next

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Andrew Morton <akpm@...>
To: <linux-next@...>
Cc: Steven French <sfrench@...>, Steven Whitehouse <swhiteho@...>, Stefan Richter <stefanr@...>, Jeff Garzik <jeff@...>, Ralf Baechle <ralf@...>, Pierre Ossman <drzeus-list@...>, Jan Kara <jack@...>, Anton Vorontsov <cbou@...>, Jens Axboe <jens.axboe@...>, Eric Van Hensbergen <ericvh@...>, Wim Van Sebroeck <wim@...>, Christian Zankel <chris@...>, Nicolas Pitre <nico@...>, Pekka Enberg <penberg@...>, Christoph Lameter <clameter@...>, Erez Zadok <ezk@...>, <linux-kernel@...>
Subject: git trees which are not yet in linux-next
Date: Friday, May 2, 2008 - 6:12 pm

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)
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 6:12 pm)
Re: git trees which are not yet in linux-next, Pierre Ossman, (Tue May 13, 2:36 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 13, 3:00 am)
Re: git trees which are not yet in linux-next, Pierre Ossman, (Tue May 13, 6:47 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 13, 8:33 am)
Re: git trees which are not yet in linux-next, Pekka Enberg, (Mon May 5, 2:16 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Mon May 5, 2:31 pm)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 12:43 am)
Re: git trees which are not yet in linux-next, Pekka J Enberg, (Mon May 5, 2:41 pm)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 12:41 am)
Re: git trees which are not yet in linux-next, Daniel Hazelton, (Mon May 5, 5:11 pm)
Re: git trees which are not yet in linux-next, Stefan Richter, (Mon May 5, 3:40 pm)
Re: git trees which are not yet in linux-next, Liam Girdwood, (Mon May 5, 12:52 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Mon May 5, 1:57 pm)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 12:45 am)
Re: git trees which are not yet in linux-next, Andrew Morton, (Tue May 6, 1:50 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Tue May 6, 3:18 am)
Re: git trees which are not yet in linux-next, Stefan Richter, (Fri May 2, 9:11 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 9:18 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 6:42 pm)
Re: git trees which are not yet in linux-next, Stefan Richter, (Fri May 2, 9:19 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 9:34 pm)
Re: git trees which are not yet in linux-next, Jeff Garzik, (Sat May 3, 12:52 am)
Re: git trees which are not yet in linux-next, Stefan Richter, (Sat May 3, 4:46 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Sun May 4, 8:18 pm)
Re: git trees which are not yet in linux-next, Jeff Garzik, (Fri May 2, 6:20 pm)
Re: git trees which are not yet in linux-next, Andrew Morton, (Fri May 2, 6:33 pm)
Re: git trees which are not yet in linux-next, Jeff Garzik, (Sat May 3, 12:54 am)
Re: git trees which are not yet in linux-next, Stephen Rothwell, (Sat May 3, 12:33 am)