Linux PCI Non-Transparent Bridge framework and drivers
 help / color / mirror / Atom feed
From: "Allen Hubbe" <Allen.Hubbe@emc.com>
To: 'Baruch Siach' <baruch@tkos.co.il>,
	'Jon Mason' <jdmason@kudzu.us>,
	'Dave Jiang' <dave.jiang@intel.com>
Cc: linux-ntb@googlegroups.com
Subject: RE: [PATCH] NTB: doc: remove underscore escaping
Date: Wed, 3 Feb 2016 13:10:51 -0500	[thread overview]
Message-ID: <000001d15eae$393fd4a0$abbf7de0$@emc.com> (raw)
In-Reply-To: <8b17fab4dd0a98d2b19d40b000b81312de551732.1454485437.git.baruch@tkos.co.il>

> From: Baruch Siach
> This escaping sequence makes the plain text file hard to read, and
> obscures the
> name of identifies like module parameters. This is probably a left over
> from a
> markup version of the text.

s/identifies/identifiers/

Rather than guessing the original intent, you can say, "This is an artifact left over from formatting the document as markdown."

> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

> -### NTB Transport Client (ntb\_transport) and NTB Netdev (ntb\_netdev)
> +### NTB Transport Client (ntb_transport) and NTB Netdev (ntb_netdev)

You are correct.  The escaping of underscore is to avoid italicizing the text between underscores when the document is processed with markdown.  The escaping is intentional.

There is not much by way of official guidance around the use or non-use of markup/markdown/asciidoc in Linux/Documentation (or, I have not found it - please direct me).  There are a few other files under Documentation with similar markup; most seem to be related to acpi.  It seems to me that subsystems like acpi have autonomy in deciding how to markup their own documentation.  There is also value in being consistent, and documents with markup are distinctly in the minority.  I also recognize your point about the markup making the plain text marginally harder to read.

On the other hand, anyone familiar with markdown will recognize the section headings, fixed width annotations, and preformatted blocks.  Someone might take this document, recognize the format, and process it with markdown.  If the escaping is taken away, the result of processing will look strange.  Therefore, if the underscore escaping is to be removed, I would rather see the whole document changed in such a way that makes it obvious that the document is not markdown.

I would leave it in, but I will not stand in the way if Jon and Dave would rather take it out.

Allen


      reply	other threads:[~2016-02-03 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03  7:43 [PATCH] NTB: doc: remove underscore escaping Baruch Siach
2016-02-03 18:10 ` Allen Hubbe [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='000001d15eae$393fd4a0$abbf7de0$@emc.com' \
    --to=allen.hubbe@emc.com \
    --cc=baruch@tkos.co.il \
    --cc=dave.jiang@intel.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-ntb@googlegroups.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