Unifying all Linux ports into one tree
I'm working towards merging all ports into one unify tree to push this to Linus. Here is a readmap.
Who is who for all Linux ports
Architecture
Responsible Person
Web Site
Mailing List
alpha
Richard Henderson <rth@twiddle.net>, Ivan Kokshaysky <ink@jurassic.park.msu.ru>
arm
Russell King <rmk@arm.linux.org.uk>
arm/pt (what's this exactly?)
Stefan Eletzhofer <tefan.eletzhofer@eletztrick.de>
arm/shark (what's this exactly?)
Alexander Schulz <alex@shark-linux.de>
cris
Bjorn Wesen <bjornw@axis.com>
h8300 (what's this exactly?)
ia64
David Mosberger-Tang <davidm@hpl.hp.com>
m68k
Jes Sorensen <jes@trained-monkey.org>
m68k/apple
Joshua Thompson <funaho@jurai.org>
m68k/hp9k-300
Philip Blundell <philb@gnu.org>
m68k/sun3
Sam Creasey <sammy@sammy.net>
m68knommu
Greg Ungerer <gerg@snapgear.com>, David McCullough <davidm@snapgear.com>
mips
Ralf Bächle <ralf@linux-mips.org>
parisc
Matthew Wilcox <matthew@wil.cx>, Grant Grundler <grundler@parisc-linux.org>
i386/visws
Andrey Panin <pazke@orbita1.ru>
i386/pc9800
Osamu Tomita <tomita@cinet.co.jp>
ppc
Benjamin Herrenschmidt <benh@kernel.crashing.org>, Roman Zippel <zippel@linux-m68k.org>
ppc64
David Engebretsen <engebret@us.ibm.com>
s390
Martin Schwidefsky <schwidefsky@de.ibm.com>
http://oss.software.ibm.com/developerworks/opensource/linux390
sh
Niibe Yutaka <gniibe@m17n.org>
sparc
Pete Zaitcev <zaitcev@redhat.com>, Dave S. Miller <davem@redhat.com
sparc64
Dave S. Miller <davem@redhat.com>
um
Jeff Dike <jdike@karaya.com>
v850
Miles Bader <miles@lsi.nec.co.jp>
x86_64
Andi Kleen <ak@suse.de>
Step 1: Get Data
Before starting anything, we have to get informed. This is why I'm planing to send an email with about this content:
Dear Port-Maintainer, you're maintaing one or more Linux ports to different hardware. I'm currently planing to end the life of a dozend different Linux trees, one for each architecture. Instead of this, I'd like to have _one_ tree useable for all supported architectures. I'm planing to merge all Linux trees, this is why I've got some questions I'm kindly asking you to answer: I'm _________________ <_______@___________> and I'm maintaining Linux port(s) to the _____________ architecture. For my architecture, I'm using [ ] 2.4.x or [ ] 2.5.x. My trees are in this state: | 2.4.x | 2.5.x --------------------------+-----------+--------- Keeping up'to'date | [ ] | [ ] with Marcelo's / Linus' | | tree including at least | | -preX and -rcX releases, | | possibly even their BK | | trees | | --------------------------+-----------+--------- I'm only syncing with | [ ] | [ ] full releases (no -rcX | | or -preX releases) | | --------------------------+-----------+--------- I'm only occassionally | [ } | [ ] resyncing with Marcelo/ | | Linus | | --------------------------+-----------+--------- Ny Scource Code Management| | System is (CVS/BK/ | | ClearCase/homegrown/...) | | --------------------------+-----------+--------- My current tree is | | available at / not | | available at all | | --------------------------+-----------+--------- I think it would simplify | [ } | [ ] my work if I could do | | development on a global | | tree and it would be | | sinpler to avoid global | | breakages | | --------------------------+-----------+--------- I'm willing to help | [ ] | [ ] achieving the goal of a | | global tree by keeping | | my tree up-to-date wrt. | | Linus / Marcelo | | Thanks a lot! I'll contact you soon. MfG, JBG