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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 20 May 2010 09:20:30 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jiri Kosina <jkosina@...e.cz>,
	Don Prince <dhprince-devel@...oo.co.uk>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT] HID



On Wed, 19 May 2010, Jiri Kosina wrote:
> 
> please pull from 'for-linus' branch from
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
> 
> to receive HID subsystem patches queued for 2.6.35 merge window.

This is just unbelievable SH*T:

	config HID_ZYDACRON
		tristate "Zydacron remote control support" if EMBEDDED
		depends on USB_HID
		default !EMBEDDED
		---help---
		Support for Zydacron remote control.

First it says "only ask if EMBEDDED", and then it says "default to Y if 
not embedded".

Why? Why the hell did somebody decide that everybody and their pet dog 
should get that totally uninteresting driver, whether they want it or not?

I realize that every single developer thinks that their driver is the most 
important thing in the universe, but come on! This kind of thing is 
totally inappropriate, and to make matters worse, it looks like there are 
a few commits that won't even compile because the whole file wasn't even 
added until later.

And this piece of shit was made _mandatory_?

Get a grip, people. I'm not pulling idiotic crap like this. Some quality 
control before you ask me to pull, for chissake!

		Linus
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ