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]
Message-ID: <CAErSpo5Jsbh8fcUXt_GL=ihv-3yq1SOD_UejC5MP=jBGowNn_w@mail.gmail.com>
Date:	Thu, 11 Jul 2013 14:40:26 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Mark Galeck <mark_galeck@...bell.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: is it desirable to improve the build system?

On Thu, Jul 11, 2013 at 5:38 AM, Pavel Machek <pavel@....cz> wrote:
> Hi!
>>
>> Does the Linux-Kernel Community perceive that is the case?
>>
>> If so, do you think it is possible to improve?
>>
>> If so, would such an attempt be welcome, including and especially by, the current maintainer(s) of the build?  Of course it would have to be completely backwards-compatible, including to the text output interface and requirements for modules makefiles.
>>
>
> Yes, speeding up build would be nice. Especially nice would be
> speeding up "empty" build, when only one or two files changed...

The answer to "is it desirable to improve X?" is always "yes."  But
the only way to make progress in Linux is to actually post patches
that "improve X."  This is unlike many corporate environments, where
you might need to get somebody's approval before you even start
trying.  In Linux, there's no such thing as prior approval.  Even if
you could get somebody to say "this looks like a good thing to try,"
that would be no guarantee that subsequent patches would be accepted.

It's hard enough to get people to comment on actual Linux code
changes, i.e., patches.  It's almost impossible to get useful feedback
on proposals without code.

If you posted patches that made significant improvements in build
time, I think people would be very interested.

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