| 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, 20 Aug 2008 05:43:52 +0200 From: Marcel Holtmann <marcel@...tmann.org> To: David Miller <davem@...emloft.net> Cc: torvalds@...ux-foundation.org, akpm@...ux-foundation.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [GIT]: Networking Hi Dave, > > For example, those BT updates looked in no way like regression fixes. So > > what the f*ck were they doing there? And why do you think all those driver > > updates cannot cause new regressions? > > The BT bits were the only part I really considered borderline, > and I was going to push back on Marcel. > > But to be honest, I haven't seen bluetooth updates from him > for such a long time I felt that being strict here would just > exacerbate the problem. > > Guess I was wrong. as I explained to Linus, my current assumption was that documentation updates and new driver stuff should go in quickly. You will not get any of these from me anymore. Next time you only get the one regression fix and all my queued up stuff in the next merge window. Don't hold back if you think that a patch is not acceptable. Really, I am using GIT for everything. Merging is no problem for me. I also do backports in my -mh patch for the latest stable kernel. So there is no extra work for me. It is just sending you a new email with another tree to pull from :) Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists