From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: "John Snow" <jsnow@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [qemu-web PATCH] Update website to point to the new bug tracker at GitLab instead of Launchpad
Date: Mon, 3 May 2021 12:30:07 +0200 [thread overview]
Message-ID: <20210503103007.1034171-1-thuth@redhat.com> (raw)
We've started migrating the bug tickets from Launchpad to GitLab, so
it does not make too much sense anymore that users open new tickets
in the old system. Let's direct them now to the GitLab tracker instead.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
contribute.md | 3 ++-
contribute/report-a-bug.md | 5 ++++-
support.md | 2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/contribute.md b/contribute.md
index d7e295f..cbb476d 100644
--- a/contribute.md
+++ b/contribute.md
@@ -3,7 +3,8 @@ title: Contribute to QEMU!
permalink: /contribute/
---
-* Report a bug in our bugtracker: [https://bugs.launchpad.net/qemu/](https://bugs.launchpad.net/qemu/)<br>
+* Report a bug in our bugtracker:
+ <https://gitlab.com/qemu-project/qemu/-/issues><br/>
See also [How to report a bug](report-a-bug/) or [How to report a security bug](security-process/)
* Clone ([or browse](https://gitlab.com/qemu-project/qemu)) the git repository: <br>`git clone https://gitlab.com/qemu-project/qemu.git`
diff --git a/contribute/report-a-bug.md b/contribute/report-a-bug.md
index 1cc42e7..922f699 100644
--- a/contribute/report-a-bug.md
+++ b/contribute/report-a-bug.md
@@ -3,7 +3,10 @@ title: Reporting a bug
permalink: /contribute/report-a-bug/
---
-Bugs can be filed at our [bug tracker](https://bugs.launchpad.net/qemu/), which is hosted on Launchpad. If you've got a problem with how your Linux distribution packages QEMU, use the bug tracker from your distro instead.
+Bugs can be filed at our
+[bug tracker](https://gitlab.com/qemu-project/qemu/-/issues), which is hosted
+on GitLab. Note: If you've got a problem with how your Linux distribution
+packages QEMU, please use the bug tracker from your distro instead.
When submitting a bug report, please try to do the following:
diff --git a/support.md b/support.md
index 252351c..b622362 100644
--- a/support.md
+++ b/support.md
@@ -41,5 +41,5 @@ response. If you can't leave IRC open and wait you may be better
served by a mailing list.
* If you think you have found a bug you can report it on [our bug
- tracker](https://bugs.launchpad.net/qemu/).<br>
+ tracker](https://gitlab.com/qemu-project/qemu/-/issues).<br/>
Please see our guide on [how to report a bug](/contribute/report-a-bug/)
--
2.27.0
next reply other threads:[~2021-05-03 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 10:30 Thomas Huth [this message]
2021-05-03 10:47 ` [qemu-web PATCH] Update website to point to the new bug tracker at GitLab instead of Launchpad Philippe Mathieu-Daudé
2021-05-03 10:56 ` Thomas Huth
2021-05-03 13:05 ` Philippe Mathieu-Daudé
2021-05-03 23:26 ` John Snow
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=20210503103007.1034171-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).