From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Roland Hieber Date: Tue, 8 Oct 2019 12:07:55 +0200 Message-Id: <20191008100756.27371-1-rhi@pengutronix.de> MIME-Version: 1.0 Subject: [ptxdist] [PATCH 1/2] doc: dev manual: patches: clean up literal formatting List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de Cc: Roland Hieber Make variable formatting consistent with the rest of the document by using reST syntax instead of Markdown syntax. Signed-off-by: Roland Hieber --- 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 `` 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 ```` 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