From: Paul Bolle <pebolle@tiscali.nl>
To: Ulf Magnusson <ulfalizer.lkml@gmail.com>
Cc: Andreas Ruprecht <andreas.ruprecht@fau.de>,
Valentin Rothberg <valentinrothberg@gmail.com>,
rafael.j.wysocki@intel.com, linux-kbuild@vger.kernel.org,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
hengelein Stefan <stefan.hengelein@fau.de>,
linux@dominikbrodowski.net
Subject: Re: Kconfig: '+config' valid syntax?
Date: Fri, 03 Jul 2015 13:00:49 +0200 [thread overview]
Message-ID: <1435921249.2423.70.camel@tiscali.nl> (raw)
In-Reply-To: <CAEMqcmoTHxOGRdRFMrY=kkG4HzD7vNUHVwZCsGDabGUOxhsvOQ@mail.gmail.com>
On vr, 2015-07-03 at 12:46 +0200, Ulf Magnusson wrote:
> Except for scattered accidents like in the original message, which are
> hopefully pretty rare and easy to fix,
Correct.
> the only documented thing that depends
> on that lexer sloppiness is the ---help--- "token".
>
> I'd just add "---help---" as another T_HELP alias
Which implies dropping the empty rule for "---", right?
> (or get rid of it altogether,
> but that's probably more work than it's worth).
$git grep -e "---help---" -- "*Kconfig*" | wc -l
2590
Doable. Might not make you friends.
> Tightening things up should be safe after that.
Did you already try adding ---help--- (and something similar to Andreas'
check for the mistake we're discussing here)?
Paul Bolle
next prev parent reply other threads:[~2015-07-03 11:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 8:08 Kconfig: '+config' valid syntax? Valentin Rothberg
2015-07-02 9:01 ` Paul Bolle
2015-07-02 9:25 ` Paul Bolle
2015-07-02 11:57 ` Andreas Ruprecht
2015-07-02 12:10 ` Paul Bolle
2015-07-03 7:33 ` Andreas Ruprecht
2015-07-03 8:59 ` Paul Bolle
2015-07-03 9:29 ` Andreas Ruprecht
2015-07-03 10:46 ` Ulf Magnusson
2015-07-03 10:51 ` Valentin Rothberg
2015-07-03 10:56 ` Stefan Hengelein
2015-07-03 11:11 ` Stefan Hengelein
2015-07-03 11:34 ` Ulf Magnusson
2015-07-03 11:00 ` Paul Bolle [this message]
2015-07-03 11:33 ` Andreas Ruprecht
2015-07-03 11:40 ` Ulf Magnusson
2015-07-03 12:39 ` Ulf Magnusson
2015-07-03 12:48 ` Ulf Magnusson
2015-07-03 11:58 ` Paul Bolle
2015-07-03 10:52 ` Paul Bolle
2015-07-02 19:59 ` Rafael J. Wysocki
2015-07-03 10:16 ` Ulf Magnusson
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=1435921249.2423.70.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=andreas.ruprecht@fau.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rafael.j.wysocki@intel.com \
--cc=stefan.hengelein@fau.de \
--cc=ulfalizer.lkml@gmail.com \
--cc=valentinrothberg@gmail.com \
/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