mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 1/2] doc: dev manual: patches: clean up literal formatting
Date: Tue,  8 Oct 2019 12:07:55 +0200	[thread overview]
Message-ID: <20191008100756.27371-1-rhi@pengutronix.de> (raw)

Make variable formatting consistent with the rest of the document by
using reST syntax instead of Markdown syntax.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 doc/dev_manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst
index 3dcaeb3d31fa..c370940906ea 100644
--- a/doc/dev_manual.rst
+++ b/doc/dev_manual.rst
@@ -1265,9 +1265,9 @@ integrated into your BSP or into PTXdist.
 
 PTXdist handles patching automatically.
 After extracting the archive of a package, PTXdist checks for the existence of
-a patch directory named like its `<PKG>` variable.
-Take an exemplary package `foo` with version `1.1.0`:
-The variable `FOO` will have the value ``foo-1.1.0``, so PTXdist will look for
+a patch directory named like its ``<PKG>`` variable.
+Take an exemplary package ``foo`` with version ``1.1.0``:
+The variable ``FOO`` will have the value ``foo-1.1.0``, so PTXdist will look for
 a patch directory named ``foo-1.1.0`` in the following locations:
 
 #. the current layer:
-- 
2.20.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2019-10-08 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 10:07 Roland Hieber [this message]
2019-10-08 10:07 ` [ptxdist] [PATCH 2/2] doc: dev/ref manual: describe the <PKG>_PATCHES variable Roland Hieber

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=20191008100756.27371-1-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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