From: Sam Ravnborg <sam@ravnborg.org>
To: Jaswinder Singh <jaswinderlinux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22.7 autoconf.h is screwed up
Date: Tue, 25 Sep 2007 08:16:37 +0200 [thread overview]
Message-ID: <20070925061637.GB10029@uranus.ravnborg.org> (raw)
In-Reply-To: <3f9a31f40709240506s2befe4eu6c1c5411599d1343@mail.gmail.com>
Hi Jaswinder.
On Mon, Sep 24, 2007 at 05:36:43PM +0530, Jaswinder Singh wrote:
> 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.
Part of a larger change. git has full history.
Try to look here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=scripts/kconfig/confdata.c;h=b2913e9da495bf921b9d004012adef18996f4efa;hb=HEAD
It is the changes around 2006-06-09
Sam
prev parent reply other threads:[~2007-09-25 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 10:20 Jaswinder Singh
2007-09-24 10:26 ` Robert P. J. Day
2007-09-24 10:35 ` Jaswinder Singh
2007-09-24 10:37 ` Robert P. J. Day
2007-09-24 10:46 ` Jaswinder Singh
2007-09-24 10:49 ` Robert P. J. Day
2007-09-24 10:55 ` Jaswinder Singh
2007-09-25 7:10 ` Jan Engelhardt
2007-09-24 11:57 ` Sam Ravnborg
2007-09-24 12:06 ` Jaswinder Singh
2007-09-25 6:16 ` Sam Ravnborg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070925061637.GB10029@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®