From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, michael.roth@amd.com, jsnow@redhat.com
Subject: Re: [PATCH] qapi: Improve error message for description following section
Date: Wed, 10 May 2023 16:40:28 +0200 [thread overview]
Message-ID: <875y908d2b.fsf@secure.mitica> (raw)
In-Reply-To: <20230510141637.3685080-1-armbru@redhat.com> (Markus Armbruster's message of "Wed, 10 May 2023 16:16:37 +0200")
Markus Armbruster <armbru@redhat.com> wrote:
> The error message is bad when the section is untagged. For instance,
> test case doc-interleaved-section produces "'@foobar:' can't follow
> 'Note' section", which is okay, but if we drop the "Note:" tag, we get
> "'@foobar:' can't follow 'None' section, which is bad.
>
> Change the error message to "description of '@foobar:' follows a
> section".
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
prev parent reply other threads:[~2023-05-10 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 14:16 [PATCH] qapi: Improve error message for description following section Markus Armbruster
2023-05-10 14:40 ` Juan Quintela [this message]
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=875y908d2b.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=michael.roth@amd.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.