DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=dSEsAvFgWMP52JdLwV8PauvEfTbf8BNZnDuqtSBOitKfwSzV9tI4jaN39xZKLjfu3Iq+7EeJrxaXU3GTpPkBbi26SEIpXcBNalZzaAqcRi/aYABsSC/6anmdjRL/Zh3fMi5F6kcLlS8WFeK1m0B/vqu+vsBe2ar0rL97dN8lwU4=
Message-ID: <3f9a31f40709240506s2befe4eu6c1c5411599d1343@mail.gmail.com>
Date: Mon, 24 Sep 2007 17:36:43 +0530
From: "Jaswinder Singh" <jaswinderlinux@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: 2.6.22.7 autoconf.h is screwed up
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20070924115749.GB3150@uranus.ravnborg.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3f9a31f40709240320mb213a7an87cee8bf5517d7f7@mail.gmail.com>
	 <20070924115749.GB3150@uranus.ravnborg.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 881
Lines: 27

Dear Sam,

On 9/24/07, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
> > Hi all,
> >
> > 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> > compare to 2.6.10's autoconf.h .
> >
> > 2.6.22.7 totally changed the meaning of autoconf.h
>
> autoconf.h has always been autogenerated. And autoconf.h has always
> been used to publish the configuration to .c files.
>
> What changed between 2.6.10 and 26.22 are the algorithm used to
> produce autoconf.h.

I just curious, how algorithm is written that it makes readable to non-readable.

Thank you,

Jaswinder Singh.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/