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:	Wed, 7 Feb 2007 15:52:54 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Roman Zippel <zippel@...ux-m68k.org>
cc:	Oleg Verych <olecom@...wer.upol.cz>,
	Alexey Dobriyan <adobriyan@...il.com>, sam@...nborg.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kai Germaschewski <kai@...maschewski.name>
Subject: Re: [patch, fix build regression] kbuild: Kbuild.include avoid using
 spaces in call arguments



On Thu, 8 Feb 2007, Roman Zippel wrote:
> 
> Sorry, it needs more changes, the patch simply wasn't ready.

One problem I find very problematic with all the Kbuild setup is that 
people tend to be very quiet about any build issues until they simply go 
in.

Things don't "get ready" on their own. In other areas, people comment on 
why they don't like patches. In Kbuild, for some reason, we often seem to 
have this situation where people don't react at all.

Sam is great about maintaining the kernel build stuff most of the time, 
but because it's clearly a "secondary" thing, there tends to be some 
periods when nothing happens. Which is problematic for me..

So I end up in a situation where I just basically will apply the patches 
just becauseif I don't, nothing ever happens. The good news is that _once_ 
I apply them, people will usually notice problems and send in fixes fairly 
quickly. But this particular email was NOT useful, for example.  "needs 
more changes" is the epitome of a "not useful" comment.

I notice that Kai should probably have been Cc'd, and quite possibly 
wasn't. So I added him now.

In the meantime, I've applied the fixup patch. And more specific problem 
reports or patches are welcome.

		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