mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 17:39:31 +00:00
Code Issues Projects Releases Wiki Activity

sphinx: replace special quotes with single and double quotes

Browse Source 
(From yocto-docs rev: 0aeb7a94abcef3cb3850c753dd0a243f381e6675)

Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz
2020-09-17 01:58:59 +02:00
committed by Richard Purdie
parent 6813141743
commit c387f0c254
26 changed files with 106 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/dev-manual/dev-manual-common-tasks.rst
+3 -3
View File
@@ -6111,7 +6111,7 @@ the existing kernel, and then inserts a new kernel:
If you see the following error, you need to update or create a
~/.mtoolsrc
file and be sure to have the line “mtools_skip_check=1“ in the
file and be sure to have the line "mtools_skip_check=1" in the
file. Then, run the Wic command again:
::
@@ -7157,7 +7157,7 @@ variable to specify the format:
2. Select the desired package format as follows:
::
PACKAGE_CLASSES ?= “package_packageformat”
PACKAGE_CLASSES ?= "package_packageformat"
where packageformat can be "ipk", "rpm",
"deb", or "tar" which are the supported package formats.
@@ -10372,7 +10372,7 @@ debugger.
an image recipe:
::
IMAGE_INSTALL_append = “ gdbserver"
IMAGE_INSTALL_append = " gdbserver"
The change makes
sure the ``gdbserver`` package is included.
documentation/dev-manual/dev-manual-common-tasks.xml
+3 -3
View File
@@ -8384,7 +8384,7 @@
If you see the following error, you need to
update or create a
<filename>~/.mtoolsrc</filename> file and
be sure to have the line “mtools_skip_check=1“
be sure to have the line "mtools_skip_check=1"
in the file.
Then, run the Wic command again:
<literallayout class='monospaced'>
@@ -9837,7 +9837,7 @@
<listitem><para>
Select the desired package format as follows:
<literallayout class='monospaced'>
PACKAGE_CLASSES ?= “package_<replaceable>packageformat</replaceable>”
PACKAGE_CLASSES ?= "package_<replaceable>packageformat</replaceable>"
</literallayout>
where <replaceable>packageformat</replaceable>
can be "ipk", "rpm", "deb", or "tar" which are the
@@ -14193,7 +14193,7 @@
<filename>local.conf</filename> file or in an image
recipe:
<literallayout class='monospaced'>
IMAGE_INSTALL_append = “ gdbserver"
IMAGE_INSTALL_append = " gdbserver"
</literallayout>
The change makes sure the <filename>gdbserver</filename>
package is included.
documentation/dev-manual/dev-manual-qemu.rst
+4 -4
View File
@@ -74,7 +74,7 @@ available. Follow these general steps to run QEMU:
3. *Ensure the Artifacts are in Place:* You need to be sure you have a
pre-built kernel that will boot in QEMU. You also need the target
root filesystem for your target machine’s architecture:
root filesystem for your target machine's architecture:
- If you have previously built an image for QEMU (e.g. ``qemux86``,
``qemuarm``, and so forth), then the artifacts are in place in
@@ -396,7 +396,7 @@ command line:
- ROOTFS: A root filesystem that has one of the following filetype
extensions: "ext2", "ext3", "ext4", "jffs2", "nfs", or "btrfs". If
the filename you provide for this option uses “nfs”, it must provide
the filename you provide for this option uses "nfs", it must provide
an explicit root filesystem path.
- KERNEL: A kernel image, which is a ``.bin`` file. When you provide a
@@ -405,7 +405,7 @@ command line:
- MACHINE: The architecture of the QEMU machine, which must be one of
the following: "qemux86", "qemux86-64", "qemuarm", "qemuarm64",
"qemumips", “qemumips64", or "qemuppc". The MACHINE and QEMUARCH
"qemumips", "qemumips64", or "qemuppc". The MACHINE and QEMUARCH
options are basically identical. If you do not provide a MACHINE
option, ``runqemu`` tries to determine it based on other options.
@@ -465,6 +465,6 @@ command line:
``/dev/vhost-net``.
- The build host ``/dev/vhost-net`` directory has to be either
readable or writable and “slirp-enabled”.
readable or writable and "slirp-enabled".
- ``publicvnc``: Enables a VNC server open to all hosts.
documentation/dev-manual/dev-manual-qemu.xml
+4 -4
View File
@@ -106,7 +106,7 @@
You need to be sure you have a pre-built kernel that
will boot in QEMU.
You also need the target root filesystem for your target
machine’s architecture:
machine's architecture:
<itemizedlist>
<listitem><para>
If you have previously built an image for QEMU
@@ -553,7 +553,7 @@
A root filesystem that has one of the following
filetype extensions: "ext2", "ext3", "ext4", "jffs2",
"nfs", or "btrfs".
If the filename you provide for this option uses “nfs”, it
If the filename you provide for this option uses "nfs", it
must provide an explicit root filesystem path.
</para></listitem>
<listitem><para>
@@ -567,7 +567,7 @@
<replaceable>MACHINE</replaceable>:
The architecture of the QEMU machine, which must be one
of the following: "qemux86", "qemux86-64", "qemuarm",
"qemuarm64", "qemumips", “qemumips64", or "qemuppc".
"qemuarm64", "qemumips", "qemumips64", or "qemuppc".
The <replaceable>MACHINE</replaceable> and
<replaceable>QEMUARCH</replaceable> options are basically
identical.
@@ -674,7 +674,7 @@ qemux86" or "qemux86-64".
<listitem><para>
The build host <filename>/dev/vhost-net</filename>
directory has to be either readable or writable
and “slirp-enabled”.
and "slirp-enabled".
</para></listitem>
</itemizedlist>
</para></listitem>