linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Masami Hiramatsu <mhiramat@kernel.org>, linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [v2 0/1] Documentation: bootconfig: Documentation updates
Date: Fri, 28 Feb 2020 10:00:55 +0100	[thread overview]
Message-ID: <957cef56-04b0-3889-6c95-a8ed7606b68d@web.de> (raw)
In-Reply-To: <158287861133.18632.12035327305997207220.stgit@devnote2>

> I decided to drop EBNF (extended Backus–Naur form) patch
> since the ISO/IEC 14977 EBNF seems not carefully defined

Significant efforts happened also for this standard.
Does its revision refer still to the year 1996?


> and there are many variants which named EBNF.
> I'll postpone it until finding better solution.

How will the corresponding clarification evolve?


I hope that typos will be avoided also in subjects of subsequent cover letters.

Regards,
Markus

  parent reply	other threads:[~2020-02-28  9:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  8:30 [PATCH v2 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-02-28  8:30 ` [PATCH v2] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-02-28 10:00   ` Markus Elfring
2020-02-28 13:26     ` Masami Hiramatsu
2020-02-28 11:55   ` [v2] " Markus Elfring
2020-02-29  5:59   ` [PATCH v2] " Randy Dunlap
2020-03-02  6:52     ` Masami Hiramatsu
2020-03-02  7:06       ` Randy Dunlap
2020-03-02  8:23       ` [v2] " Markus Elfring
2020-02-28  9:00 ` Markus Elfring [this message]
2020-02-28 13:23   ` [v2 0/1] Documentation: bootconfig: Documentation updates Masami Hiramatsu
2020-02-28 14:05     ` Markus Elfring
2020-02-28 14:55       ` Masami Hiramatsu

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=957cef56-04b0-3889-6c95-a8ed7606b68d@web.de \
    --to=markus.elfring@web.de \
    --cc=corbet@lwn.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).