[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.1.10.0804240930180.15791@fbirervta.pbzchgretzou.qr>
Date: Thu, 24 Apr 2008 09:31:31 +0200 (CEST)
From: Jan Engelhardt <jengelh@...putergmbh.de>
To: Jesper Juhl <jesper.juhl@...il.com>
cc: "devzero@....de" <devzero@....de>, linux-kernel@...r.kernel.org,
agruen@...e.de
Subject: Re: make cloneconfig ?
On Thursday 2008-04-24 00:43, Jesper Juhl wrote:
>> any reason why "make cloneconfig" never made it into mainline?
>>
>> many people are quite used to it and every time i build vanilla kernel i step into that trap "oh - that`s a suse`ism"
>>
>> make cloneconfig exists since /proc/config.gz - but while that one went into mainline, cloneconfig never did.
>>
>> anyone know the reason for that ?
>>
>> i wished, distros kernels were more similar to vanilla kernels - so what about making them more similar ?
>>
>>
>
>Isn't "cloneconfig" basically just "zcat /proc/config.gz > .config &&
>make oldconfig" ??? If so, why do we need yet another "make
><some_target>" Makefile rule? What would actually be gained?
Not just that, it also searches /boot/config-... (a redhatism)
and /lib/modules/.../.config.
So it's not like it would be a suse-only shortcut.
--
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