From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, eblake@redhat.com
Subject: [Qemu-devel] [qemu-web PATCH] move bug reporting instructions from wiki to www
Date: Wed, 26 Jul 2017 13:10:49 +0200 [thread overview]
Message-ID: <20170726111049.18030-1-pbonzini@redhat.com> (raw)
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>
---
| 2 +-
contribute.md | 2 +-
contribute/report-a-bug.md | 19 +++++++++++++++++++
3 files changed, 21 insertions(+), 2 deletions(-)
create mode 100644 contribute/report-a-bug.md
--git a/_includes/footer.html b/_includes/footer.html
index cd28480..7a3e8b1 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -7,9 +7,9 @@
</ul>
<ul class="style">
<li><a href="/contribute">Contribute</a></li>
+ <li><a href="/contribute/report-a-bug">Reporting a bug</a></li>
<li><a href="http://wiki.qemu-project.org/Documentation/GettingStartedDevelopers">New contributors</a></li>
<li><a href="http://wiki.qemu-project.org/Contribute/SubmitAPatch">Submitting a patch</a></li>
- <li><a href="http://wiki.qemu-project.org/Contribute/ReportABug">Reporting a bug</a></li>
<li><a href="http://wiki.qemu-project.org/Contribute/FAQ">Contributor FAQ</a></li>
</ul>
<ul class="style">
diff --git a/contribute.md b/contribute.md
index fb2238d..e052654 100644
--- a/contribute.md
+++ b/contribute.md
@@ -3,7 +3,7 @@ title: Contribute to QEMU!
permalink: /contribute/
---
-* Report a bug: https://bugs.launchpad.net/qemu/<br>[How to report a bug](http://wiki.qemu-project.org/Contribute/ReportABug)
+* Report a bug: https://bugs.launchpad.net/qemu/<br>[How to report a bug](report-a-bug/)
* Clone the git repository: <br>`git clone git://git.qemu-project.org/qemu.git`
diff --git a/contribute/report-a-bug.md b/contribute/report-a-bug.md
new file mode 100644
index 0000000..f0fd67b
--- /dev/null
+++ b/contribute/report-a-bug.md
@@ -0,0 +1,19 @@
+---
+title: Reporting a bug
+permalink: /contribute/report-a-bug
+---
+
+Bugs can be filed at our [https://bugs.launchpad.net/qemu/ bug tracker].
+
+When submitting a bug report, please try to do the following:
+
+* 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.
+
+* Include the full command line used to launch the QEMU guest.
+
+* Reproduce the problem directly with a QEMU command-line. Avoid frontends and management stacks, to ensure that the bug is in QEMU itself and not in a frontend.
+
+* Include as information about the guest (operating system, version, 32/64-bit).
+
+* Do not contribute patches on the bug tracker; send patches to the mailing list. Follow QEMU's [guidelines about submitting patches](http://wiki.qemu.org/Contribute/SubmitAPatch).
+
--
2.13.3
next reply other threads:[~2017-07-26 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:10 Paolo Bonzini [this message]
2017-07-26 11:18 ` [Qemu-devel] [qemu-web PATCH] move bug reporting instructions from wiki to www Eric Blake
2017-07-26 11:32 ` Thomas Huth
2017-07-26 11:37 ` Eric Blake
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=20170726111049.18030-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblake@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).