From: Ulf Magnusson <ulfalizer@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <mmarek@suse.com>,
Arnaud Lacombe <lacombar@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig: Sync zconf.y with zconf.tab.c_shipped
Date: Sat, 13 Jan 2018 10:32:11 +0100 [thread overview]
Message-ID: <CAFkk2KR=N+9rGbVjMwksi7fYeE1KzzDZQz9zA34PbDXVAkwwtw@mail.gmail.com> (raw)
In-Reply-To: <20180112193857.GA426@ravnborg.org>
On Fri, Jan 12, 2018 at 8:38 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> Hi Ulf, Masahiro
>
>> >
>> > BTW, I do not know the historical reason
>> > why zconf instead of kconf in the first place...
>>
>> I have no idea either. kconfig.{l,y} and kconfig_*() would be a lot
>> less confusing.
>
> zconf was the name originally invented by Roman Zippel.
> kconfig had the name "lc" in the original submission,
> but was later renamed to kconfig.
> And if memory serves me correct the original codebase used zconf.
>
> The use of Kconfig for the files was first introduced here:
> https://sourceforge.net/p/kbuild/mailman/message/8519479/
> This was before lc aka kconfig was included in the kernel.
>
> This was all in a period after the huge CML2 flamewars
> which some oldies may remember.
>
> Surfing dwom memory lane was fun - lot of mails.
>
> This was also back when Keith Ownes attempt for a new generation
> kbuild was rejected and Kai Germaschewski migrated the
> old build system to something that was good and reliable.
>
> Fun times indeed :-)
> For some of the involved this was not fun at all - investing a lot
> of time and then see it rejected is never fun.
>
> Sam
Thanks for the history lesson.
Had heard of the CML2 drama. Bit of a second-system effect going on
there I think.
Python all the way back in 2002 was unexpected. Can see why people
might have been opposed to that.
History aside, I'm all for renaming some things if anyone steps up.
Explicit naming goes a long way for me.
Cheers,
Ulf
prev parent reply other threads:[~2018-01-13 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 3:06 [PATCH] kconfig: Sync zconf.y with zconf.tab.c_shipped Ulf Magnusson
2017-12-12 14:58 ` Masahiro Yamada
2018-01-12 11:23 ` Ulf Magnusson
2018-01-12 19:38 ` Sam Ravnborg
2018-01-13 9:32 ` Ulf Magnusson [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='CAFkk2KR=N+9rGbVjMwksi7fYeE1KzzDZQz9zA34PbDXVAkwwtw@mail.gmail.com' \
--to=ulfalizer@gmail.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=sam@ravnborg.org \
--cc=yamada.masahiro@socionext.com \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).