From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig: don't silently ignore unhandled characters
Date: Thu, 06 Nov 2014 11:28:36 +0100 [thread overview]
Message-ID: <1415269716.4390.6.camel@x220> (raw)
In-Reply-To: <545B59540200007800045446@mail.emea.novell.com>
On Thu, 2014-11-06 at 10:19 +0000, Jan Beulich wrote:
> Again - this is code that gets generated by flex, and hence
> dropping it (entirely, or the hunk that changes it) will make the
> discussion re-appear the next time someone re-generates the
> file.
My public note ended with:
> I personally wouldn't bother to add this hunk, but who cares.
I guess it wasn't clear that this meant that I think that the
discussion, which I started of course, is basically moot.
Paul Bolle
next prev parent reply other threads:[~2014-11-06 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 9:05 [PATCH 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2014-11-04 14:06 ` Paul Bolle
2014-11-04 14:14 ` Jan Beulich
2014-11-05 10:36 ` Paul Bolle
2014-11-06 10:19 ` Jan Beulich
2014-11-06 10:28 ` Paul Bolle [this message]
2014-12-09 10:16 ` Paul Bolle
2014-12-19 16:31 ` Jan Beulich
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=1415269716.4390.6.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=JBeulich@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--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