public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Andreas Ruprecht <andreas.ruprecht@fau.de>,
	Valentin Rothberg <valentinrothberg@gmail.com>
Cc: rafael.j.wysocki@intel.com, linux-kbuild@vger.kernel.org,
	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 12:52:03 +0200	[thread overview]
Message-ID: <1435920723.2423.63.camel@tiscali.nl> (raw)
In-Reply-To: <559655E3.6010400@fau.de>

On vr, 2015-07-03 at 11:29 +0200, Andreas Ruprecht wrote:
> Well, as I mentioned earlier, with a patch similar to the one below
> this
> warning is also generated three times for every '---' before 'help'.

You're right, that was in your first message. It already slipped my
mind.

> So we would need to add special treatment for '-' also in the command
> case, right? But that doesn't look appealing to me, more like a dirty,
> dirty hack around the actual problem...

It seems so.

Someone ambitious might want to jump in the lex rules and see what can
be done in a clean way. (Perhaps that will start with renaming COMMAND
and PARAM and/or documenting these states.) I think I already
demonstrated that I'm too unfamiliar with lex for it to make sense to
volunteer.

Thanks,


Paul Bolle

  parent reply	other threads:[~2015-07-03 10:52 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
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 [this message]
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=1435920723.2423.63.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=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