| 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: <20080417015425.312d34c0.akpm@linux-foundation.org> Date: Thu, 17 Apr 2008 01:54:25 -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 01:45:34 -0700 (PDT) David Miller <davem@...emloft.net> wrote: > From: Andrew Morton <akpm@...ux-foundation.org> > Date: Thu, 17 Apr 2008 01:40:54 -0700 > > > By keeping all this code out of -mm you haven't solved any of the > > merge/integration problems which we had in 2.6.24-rcX. > > I think things would have been a lot easier if you had adopted > basing -mm on top of linux-next from the very start. 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. > The responsiveness to problems and merge hassles has been so much > superior and efficient from the linux-next folks for my networking > stuff, for example. It's never been like that with -mm. 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. -- 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