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:	Sat, 26 Apr 2008 10:21:33 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Adrian Bunk <bunk@...nel.org>
cc:	Adrian Bunk <bunk@...sta.de>, Sam Ravnborg <sam@...nborg.org>,
	Harvey Harrison <harvey.harrison@...il.com>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: If you want me to quit I will quit



On Sat, 26 Apr 2008, Adrian Bunk wrote:
> 
> The patch for the x86 userspace header breakage last weekend was Cc'ed 
> to you.

Yes, and I couldn't care less - it wasn't critical in any way (nobody 
should be using kernel headers directly in user space anyway, so the only 
people who could _possibly_ care were the people who build glibc releases 
etc).

IOW, it wasn't a critical bug-fix that needed to be pushed out 
aggressively.

Which means that I totally ignore a patch when I see that there are people 
who actually maintain that area (especially if I know they are responsible 
maintainers) that are also cc'd and that even reply to it.

It so happens that that patch got merged into my tree today - unrelated to 
this discussion - and it came through all the normal channels (ie the x86 
maintainer tree).

IOW, everything happened exactly the way it is SUPPOSED to happen.

That said, it also obviously does happen that I lose patches for real. 
Maybe some of them even from you. But your complaints really aren't 
sensible in this case.

			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