From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>,
"Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] RFC: unified --help information
Date: Wed, 26 Jul 2017 13:11:21 +0200 [thread overview]
Message-ID: <507e7a29-5461-e152-123e-aab9dfc1f8ac@redhat.com> (raw)
In-Reply-To: <f3b1276a-92e3-54f3-c6a0-5f8e16124014@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
On 26/07/2017 12:53, Eric Blake wrote:
>
> GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
> Full documentation at: <http://www.gnu.org/software/coreutils/ls>
> or available locally via: info '(coreutils) ls invocation'
>
> or 'm4 --help | tail -n3':
> Report bugs to: bug-m4@gnu.org
> GNU M4 home page: <http://www.gnu.org/software/m4/>
> General help using GNU software: <http://www.gnu.org/gethelp/>
>
> In our executables, we are rather inconsistent with --help
>
> qemu-nbd mentions: Report bugs to <qemu-devel@nongnu.org>
> qemu-ga mentions: Report bugs to <mdroth@linux.vnet.ibm.com>
>
> while qemu-system-*, qemu-img, and qemu-io mention nothing at all. Is
> it worth unifying these to all mention qemu-devel@nongnu.org as the
> primary bug-report site, and/or to add mention of <http://qemu.org> as a
> site for further information?
I think we should point to a more specific bugreport URL.
Currently it's http://wiki.qemu.org/Contribute/ReportABug. If we want
an URL on qemu.org, we can either add a redirect from qemu.org to the
wiki, or move the contents to qemu.org (it's static enough that it
shouldn't be a big issue). I've sent out a patch for the latter.
> Likewise, with --version, qemu-io and qemu-ga lack the git suffix
> present in qemu-system-* and just added in qemu-nbd.
>
> I can submit patches to make things consistent, and think it is 2.10
> material, but first want to get consensus on what the behavior should be.
I agree it's better to be consistent.
Paolo
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-07-26 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 10:53 [Qemu-devel] RFC: unified --help information Eric Blake
2017-07-26 11:11 ` Paolo Bonzini [this message]
2017-07-26 11:22 ` Eric Blake
2017-07-26 11:35 ` 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=507e7a29-5461-e152-123e-aab9dfc1f8ac@redhat.com \
--to=pbonzini@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@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).