linux-kernel - Re: discussion of Kbuild fixes (kbuild: Kbuild.include avoid using spaces in call arguments)

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: <Pine.LNX.4.64.0702080301590.14457@scrub.home>
Date:	Thu, 8 Feb 2007 03:05:41 +0100 (CET)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Oleg Verych <olecom@...wer.upol.cz>
cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Alexey Dobriyan <adobriyan@...il.com>, torvalds@...l.org,
	sam@...nborg.org, linux-kernel@...r.kernel.org
Subject: Re: discussion of Kbuild fixes (kbuild: Kbuild.include avoid using
 spaces in call arguments)

Hi,

On Thu, 8 Feb 2007, Oleg Verych wrote:

> -- `find | sort' in localversion (i insist on split between paths and
>     files)

make has dedicated functions for this.

> -- symlinks to /dev/null in option checking -- isn't it better to not
>    have any (though cached) access to files on filesystem, instead of to
>    /dev/null? cont.:

symlinks are not much else than special files.

> I wish to have more people to work on this (even with just comments),
> because "Kbuild.include" was only first step to reduce bloated top
> Makefile. Since then, it seems, Sam have more important things to do.

The problem is that you mix multiple changes into a single patch, but 
since kbuild is very central part that puts everything together, I don't 
think it's bad idea to be more conservative, especially if you just start 
to work on it.

bye, Roman
-
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/