qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Laurent Vivier" <laurent@vivier.eu>
Subject: [PULL 01/14] qemu-img-cmds.hx: Update comment that mentions Texinfo
Date: Tue, 13 Oct 2020 13:50:39 +0200	[thread overview]
Message-ID: <20201013115052.133355-2-laurent@vivier.eu> (raw)
In-Reply-To: <20201013115052.133355-1-laurent@vivier.eu>

From: Markus Armbruster <armbru@redhat.com>

Missed in 3c95fdef94 "Update comments in .hx files that mention
Texinfo".

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20200929075824.1517969-2-armbru@redhat.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
 qemu-img-cmds.hx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
index b89c019b76bf..cab82342358e 100644
--- a/qemu-img-cmds.hx
+++ b/qemu-img-cmds.hx
@@ -1,5 +1,5 @@
 HXCOMM Keep the list of subcommands sorted by name.
-HXCOMM Use DEFHEADING() to define headings in both help text and texi
+HXCOMM Use DEFHEADING() to define headings in both help text and rST
 HXCOMM Text between SRST and ERST are copied to rST version and
 HXCOMM discarded from C version
 HXCOMM DEF(command, callback, arg_string) is used to construct
-- 
2.26.2



  reply	other threads:[~2020-10-13 11:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 11:50 [PULL 00/14] Trivial branch for 5.2 patches Laurent Vivier
2020-10-13 11:50 ` Laurent Vivier [this message]
2020-10-13 11:50 ` [PULL 02/14] target/i386/cpu: Update comment that mentions Texinfo Laurent Vivier
2020-10-13 11:50 ` [PULL 03/14] hw/block/nvme: Simplify timestamp sum Laurent Vivier
2020-10-13 11:50 ` [PULL 04/14] tests/test-char: Use a proper fallthrough comment Laurent Vivier
2020-10-13 11:50 ` [PULL 05/14] vmdk: fix maybe uninitialized warnings Laurent Vivier
2020-10-13 11:50 ` [PULL 06/14] hw/acpi/piix4: Rename piix4_pm_add_propeties() to piix4_pm_add_properties() Laurent Vivier
2020-10-13 11:50 ` [PULL 07/14] softmmu/memory: Log invalid memory accesses Laurent Vivier
2020-10-13 11:50 ` [PULL 08/14] hw/pci: Fix typo in PCI hot-plug error message Laurent Vivier
2020-10-13 11:50 ` [PULL 09/14] block/blkdebug: fix memory leak Laurent Vivier
2020-10-13 11:50 ` [PULL 10/14] hw/char/serial: remove duplicate .class_init in serial_mm_info Laurent Vivier
2020-10-13 11:50 ` [PULL 11/14] goldfish_rtc: change MemoryRegionOps endianness to DEVICE_NATIVE_ENDIAN Laurent Vivier
2020-10-13 11:50 ` [PULL 12/14] target/sparc/int32_helper: Remove duplicated 'Tag Overflow' entry Laurent Vivier
2020-10-13 11:50 ` [PULL 13/14] mingw: fix error __USE_MINGW_ANSI_STDIO redefined Laurent Vivier
2020-10-13 11:50 ` [PULL 14/14] meson.build: drop duplicate 'sparc64' entry Laurent Vivier
2020-10-13 13:53 ` [PULL 00/14] Trivial branch for 5.2 patches Peter Maydell

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=20201013115052.133355-2-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=armbru@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).