| 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: Tue, 12 Feb 2008 19:41:00 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: James Bottomley <James.Bottomley@...senPartnership.com>, Jeff Garzik <jeff@...zik.org>, David Miller <davem@...emloft.net>, arjan@...radead.org, greg@...ah.com, sfr@...b.auug.org.au, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, linux-arch@...r.kernel.org, akpm@...ux-foundation.org Subject: Re: Announce: Linux-next (Or Andrew's dream :-)) On Tue, Feb 12, 2008 at 10:59:00AM -0800, Linus Torvalds wrote: > > > On Tue, 12 Feb 2008, Linus Torvalds wrote: > > > > In other words, I'm perfectly happy to be an a*hole and tell people that I > > simply won't merge things that cause undue API churn at all, and that were > > not thought out sufficiently. > > .. btw: I'd need to know this in advance. I usually don't see the problem > until it's too late. We could simply decide that API changes affecting more than one subsystem Must Be Serialized(tm). Explicitly. As in "any such change is posted and discussed in advance, order of merges decided upon and we have merge window for one decided set of API changes + fallout *ONLY*". With merge window in question normally taking a few days. -- 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