From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-web PATCH] move bug reporting instructions from wiki to www
Date: Wed, 26 Jul 2017 06:37:03 -0500 [thread overview]
Message-ID: <53d6e223-f5e0-8a31-4b1b-02e912a07d6e@redhat.com> (raw)
In-Reply-To: <759fddfb-8b23-db01-40c8-c4ab2d1756e6@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On 07/26/2017 06:32 AM, Thomas Huth wrote:
> On 26.07.2017 13:10, Paolo Bonzini wrote:
>> The bug reporting instructions are pretty static, and it is nicer if bug
>> reporters stay within the familiar QEMU web site layout. Move the page
>> to qemu.org.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> +* Make sure you're reporting the bug against the [latest release](/download/#source). If possible, please try to reproduce with the latest development tree too.
>
> Please add also (since it still happens way too often):
>
> * Please avoid to report bugs that you've found in the QEMU version
s/to report/reporting/
> that ships with your Linux distribution. If you've got a problem with
> the QEMU from your Linux distribution, use the bug tracker from your
> distro instead.
>
All of your suggestions look like useful additions.
--
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 --]
prev parent reply other threads:[~2017-07-26 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:10 [Qemu-devel] [qemu-web PATCH] move bug reporting instructions from wiki to www Paolo Bonzini
2017-07-26 11:18 ` Eric Blake
2017-07-26 11:32 ` Thomas Huth
2017-07-26 11:37 ` Eric Blake [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=53d6e223-f5e0-8a31-4b1b-02e912a07d6e@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).