qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@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 06:22:38 -0500	[thread overview]
Message-ID: <cc3f3aa6-155f-a50d-f89c-54effaaa69cc@redhat.com> (raw)
In-Reply-To: <507e7a29-5461-e152-123e-aab9dfc1f8ac@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

On 07/26/2017 06:11 AM, Paolo Bonzini wrote:

>>
>> 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.

So something like these two lines (via a macro) in all of the
executables, ideally at the tail end of --help output?

See <https://qemu.org/contribute/report-a-bug> for bug reports.
More information on the qemu project at <https://qemu.org>

(assuming your recent patch goes in).  I'm also open to bikeshedding on
better wording, or requests on which content is most useful vs. too verbose.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2017-07-26 11:22 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
2017-07-26 11:22   ` Eric Blake [this message]
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=cc3f3aa6-155f-a50d-f89c-54effaaa69cc@redhat.com \
    --to=eblake@redhat.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=kwolf@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@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).