Hi.
> With the exception of distribution kernels, the probability that someone
> else uses exactly the same .config I'm using is nearly zero, since the
> number of possible different .config's on a given architecture is
> something in the order of 2^1000 or one (american) billion.
>
>
One ame
On Mon, Jun 26, 2006 at 04:04:24PM -0600, Jim Cromie wrote:
>
> IOW: can we switch the default of CONFIG_NODATESTAMP ?
>
>
> Clearly, somebody has already thought about stripping the date from
> .configs,
> but it seems to me that this has been forgotten, and warrants a fresh look.
>
> - I s
On Tue, Jun 27, 2006 at 01:53:02PM -0600, Jim Cromie wrote:
> Adrian Bunk wrote:
> >On Mon, Jun 26, 2006 at 04:04:24PM -0600, Jim Cromie wrote:
> >
> >>...
> >>Since it has been so long, I'll state some obvious benefits of dropping
> >>the date:
> >>...
> >>If we drop it, then we get:
> >>
> >>-
On Mon, Jun 26, 2006 at 04:04:24PM -0600, Jim Cromie wrote:
>...
> Since it has been so long, I'll state some obvious benefits of dropping
> the date:
>...
> If we drop it, then we get:
>
> - less noise when comparing configs
> - each config is unique and fingerprintable.
> - kernel gets the conf
Adrian Bunk wrote:
> On Mon, Jun 26, 2006 at 04:04:24PM -0600, Jim Cromie wrote:
>
>> ...
>> Since it has been so long, I'll state some obvious benefits of dropping
>> the date:
>> ...
>> If we drop it, then we get:
>>
>> - less noise when comparing configs
>> - each config is unique and finger
IOW: can we switch the default of CONFIG_NODATESTAMP ?
Clearly, somebody has already thought about stripping the date from
.configs,
but it seems to me that this has been forgotten, and warrants a fresh look.
- I searched http://marc.theaimsgroup.com/?l=kbuild-devel&r=1&b=200604&w=2
for CON
