From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>,
Riku Voipio <riku.voipio@iki.fi>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Laurent Vivier <laurent@vivier.eu>,
pbonzini@redhat.com, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] maint: Include bug-reporting info in --help output.
Date: Tue, 08 Aug 2017 13:06:42 +0200 [thread overview]
Message-ID: <877eye48u5.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20170726140218.15904-4-eblake@redhat.com> (Eric Blake's message of "Wed, 26 Jul 2017 09:02:18 -0500")
Eric Blake <eblake@redhat.com> writes:
> These days, many programs are including a bug-reporting address,
> or better yet, a link to the project web site, at the tail of
> their --help output. However, we were not very consistent at
> doing so: only qemu-nbd and qemu-qa mentioned anything, with the
> latter pointing to an individual person instead of the project.
>
> Add a new #define that sets up a uniform string, mentioning both
> bug reporting instructions and overall project details, and which
> a downstream vendor could tweak if they want bugs to go to a
> downstream database. Then use it in all of our binaries which
> have --help output.
>
> The canned text intentionally references http:// instead of https://
> because our https website currently causes certificate errors in
> some browsers. That can be tweaked later once we have resolved the
> web site issued.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> include/qemu-common.h | 5 +++++
> vl.c | 4 +++-
> bsd-user/main.c | 2 ++
> linux-user/main.c | 4 +++-
> qemu-img.c | 2 +-
> qemu-io.c | 5 +++--
> qemu-nbd.c | 2 +-
> qga/main.c | 2 +-
> 8 files changed, 19 insertions(+), 7 deletions(-)
>
> diff --git a/include/qemu-common.h b/include/qemu-common.h
> index b5adbfa5e9..e751361458 100644
> --- a/include/qemu-common.h
> +++ b/include/qemu-common.h
> @@ -22,6 +22,11 @@
> #define QEMU_COPYRIGHT "Copyright (c) 2003-2017 " \
> "Fabrice Bellard and the QEMU Project developers"
>
> +/* Bug reporting information for --help arguments, About dialogs, etc */
> +#define QEMU_BUGREPORTS \
> + "See <http://qemu.org/contribute/report-a-bug> for bug reports.\n" \
"See ... for bug reports" sounds like it's about browsing existing bugs.
The web page is actually about reporting bugs. What about "for how to
report bugs"?
Since I'm basically bikeshedding already: the macro expands into more
than just bug reporting. Call it QEMU_HELP_BOTTOM? Feel free to ignore
this one.
> + "More information on the qemu project at <http://qemu.org>"
"QEMU project"
> +
> /* main function, renamed */
> #if defined(CONFIG_COCOA)
> int qemu_main(int argc, char **argv, char **envp);
Getting late for 2.10, but it's such a lovely little improvement...
next prev parent reply other threads:[~2017-08-08 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 14:02 [Qemu-devel] [PATCH for-2.10 0/3] Improved --version/--help tweaks Eric Blake
2017-07-26 14:02 ` [Qemu-devel] [PATCH 1/3] qemu-io: Give more --version information Eric Blake
2017-07-26 14:02 ` [Qemu-devel] [PATCH 2/3] qga: " Eric Blake
2017-07-26 14:02 ` [Qemu-devel] [PATCH 3/3] maint: Include bug-reporting info in --help output Eric Blake
2017-07-26 14:10 ` Peter Maydell
2017-07-26 15:02 ` Eric Blake
2017-08-08 11:06 ` Markus Armbruster [this message]
2017-08-08 11:09 ` Paolo Bonzini
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=877eye48u5.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=laurent@vivier.eu \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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.