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: Wed, 27 Aug 2008 03:32:37 -0700 (PDT) From: David Miller <davem@...emloft.net> To: tomasw@...il.com Cc: holtmann@...ux.intel.com, linville@...driver.com, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: pull request: wireless-2.6 2008-08-26 From: "Tomas Winkler" <tomasw@...il.com> Date: Wed, 27 Aug 2008 13:05:23 +0300 > There is a central problem here, since I cannot really adjust driver > development progress from obvious reason with Linux merging window. Indeed, that's exactly what your core problem is. You think it's OK to contaminate upstream just because of the way you have choosen to maintain your driver. Well guess what, it's not OK to do that, and it's absolutely not our problem that you choose to do your development in the most anti-social way possible wrt. upstream. Anyways, keep defending yourself. If you persist, I can certainly make things _really_ easy, such that if there isn't a regression list entry for the bug you are fixing and it isn't mentioned explicitly in your commit message, I simply will refuse to take your changes outside of the merge window. It's that simple. Would you like things to work that way, where I'm a hard ass, or would you like to stop defending yourself endlessly, and instead start to be reasonable? Thanks. -- 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