| 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
| ||
|
Message-Id: <20080417023331.3350e217.akpm@linux-foundation.org> Date: Thu, 17 Apr 2008 02:33:31 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: David Miller <davem@...emloft.net> Cc: mingo@...e.hu, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, tglx@...utronix.de, hpa@...or.com Subject: Re: [v2.6.26] what's brewing in x86.git for v2.6.26 On Thu, 17 Apr 2008 02:19:35 -0700 (PDT) David Miller <davem@...emloft.net> wrote: > From: Andrew Morton <akpm@...ux-foundation.org> > Date: Thu, 17 Apr 2008 01:54:25 -0700 > > > linux-next ramped up across the 2.6.25-rc window and I wanted to give it > > some time to see how it would pan out. > ... > > I don't know what you mena by this. But linux-next integrates only the > > other subsystem trees and they have rarely caused me integration problems > > against git-net. There are maybe as many as 100 "subsystem trees" hosted in -mm. Stuff like md, ipmi, tty, elf, keys, procfs, char drivers, nbd, fbdev, aoe, fuse, edac and the list goes on. Once I get -mm based on linux-next, the next step is to somehow feed those trees (well, the "stable" parts thereof) back into linux-next while not losing track of all the patches. I haven't a clue how I'll do this ;) But I haven't thought about it much yet. -- 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/
Powered by blists - more mailing lists