From c3c6de21876aad811e08538544c8fe76d22ccd09 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Fri, 16 Apr 2021 18:27:05 +0200 Subject: manuals: code insertion simplification over two lines This simplifies paragraphs ending with a colon and followed by code insertion. Automatically substituted through the command: sed -i -z "s/:\n\s*::/::/g" file.rst This generates identical HTML output. (From yocto-docs rev: 28e2192a7c12d64b68061138a9f6c796453eebb1) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/overview-manual/development-environment.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'documentation/overview-manual/development-environment.rst') diff --git a/documentation/overview-manual/development-environment.rst b/documentation/overview-manual/development-environment.rst index a33f89e4fa..1decf01e43 100644 --- a/documentation/overview-manual/development-environment.rst +++ b/documentation/overview-manual/development-environment.rst @@ -430,8 +430,7 @@ local working area (also called a branch) that tracks a specific development branch from the upstream source Git repository. in other words, you can define your local Git environment to work on any development branch in the repository. To help illustrate, consider the -following example Git commands: -:: +following example Git commands:: $ cd ~ $ git clone git://git.yoctoproject.org/poky @@ -476,8 +475,7 @@ create and checkout a local working Git branch based on a tag name. When you do this, you get a snapshot of the Git repository that reflects the state of the files when the change was made associated with that tag. The most common use is to checkout a working branch that matches a -specific Yocto Project release. Here is an example: -:: +specific Yocto Project release. Here is an example:: $ cd ~ $ git clone git://git.yoctoproject.org/poky -- cgit v1.2.3-54-g00ecf