| 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
| ||
|
Date: Thu, 8 Feb 2007 15:53:00 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Kyle McMartin <kyle@...artin.ca> Cc: linux-kernel@...r.kernel.org Subject: Re: -mm merge plans for 2.6.21 On Thu, 8 Feb 2007 18:34:49 -0500 Kyle McMartin <kyle@...artin.ca> wrote: > On Thu, Feb 08, 2007 at 03:07:10PM -0800, Andrew Morton wrote: > > I'm getting fed up of holding onto hundreds of patches against subsystem > > trees, sending them over and over again seeing and nothing happen. I sent 242 > > patches out to subsystem maintainers on Monday and look at what's still here. > > > > parisc-fix-module_param-iommu-permission.patch > > pa-risc-fix-bogus-warnings-from-modpost.patch > > use-__u64-rather-than-u64-in-parisc-statfs-structs.patch > > > > -> kyle > > > > Sorry, I thought the mails meant you were dumping to Linus. Will > merge. Once a subsystem has a subsystem tree (git or quilt) I basically never merge anything which belongs to that tree. It's always originator->mm->subsystemtree->Linus If the subsystem tree maintainer wants to tell me "I can't be bothered setting up a git pull for that, please merge it for me" then that's fine. But unless I'm told that, or unless the maintainer is vacationing or totally asleep or unless the fix has some sufficiently high obviousness*importance product, I'll just keep buffering it up. - 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