From: Thomas Huth <thuth@redhat.com>
To: "Stefan Weil" <sw@weilnetz.de>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] Update documentation to refer to new location for issues
Date: Sun, 20 Jun 2021 19:12:48 +0200 [thread overview]
Message-ID: <f2f377c2-08ee-7a48-85dc-14968b7b624a@redhat.com> (raw)
In-Reply-To: <20210619154253.553446-1-sw@weilnetz.de>
On 19/06/2021 17.42, Stefan Weil wrote:
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
>
> Another update is needed for scripts/show-fixed-bugs.sh.
Don't worry about that script, I'll remove it after the next release (v6.1)
has been done. The script is then hopefully not necessary anymore thanks to
the possibility to close bugs automatically on commit in GitLab.
> diff --git a/.github/lockdown.yml b/.github/lockdown.yml
> index 07fc2f31ee..d3546bd2bc 100644
> --- a/.github/lockdown.yml
> +++ b/.github/lockdown.yml
> @@ -14,11 +14,11 @@ issues:
> at https://gitlab.com/qemu-project/qemu.git.
> The project does not process issues filed on GitHub.
>
> - The project issues are tracked on Launchpad:
> - https://bugs.launchpad.net/qemu
> + The project issues are tracked on GitLab:
> + https://gitlab.com/qemu-project/qemu/-/issues
>
> QEMU welcomes bug report contributions. You can file new ones on:
> - https://bugs.launchpad.net/qemu/+filebug
> + https://gitlab.com/qemu-project/qemu/-/issues/new
>
> pulls:
> comment: |
> diff --git a/README.rst b/README.rst
> index a92c7394b7..79b19f1481 100644
> --- a/README.rst
> +++ b/README.rst
> @@ -131,16 +131,16 @@ will be tagged as my-feature-v2.
> Bug reporting
> =============
>
> -The QEMU project uses Launchpad as its primary upstream bug tracker. Bugs
> +The QEMU project uses GitLab issues to track bugs. Bugs
> found when running code built from QEMU git or upstream released sources
> should be reported via:
>
> -* `<https://bugs.launchpad.net/qemu/>`_
> +* `<https://gitlab.com/qemu-project/qemu/-/issues>`_
>
> If using QEMU via an operating system vendor pre-built binary package, it
> is preferable to report bugs to the vendor's own bug tracker first. If
> the bug is also known to affect latest upstream code, it can also be
> -reported via launchpad.
> +reported via GitLab.
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-06-20 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 15:42 [PATCH] Update documentation to refer to new location for issues Stefan Weil
2021-06-19 15:45 ` Philippe Mathieu-Daudé
2021-06-19 17:05 ` Alex Bennée
2021-06-20 17:12 ` Thomas Huth [this message]
2021-06-23 10:16 ` Alex Bennée
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=f2f377c2-08ee-7a48-85dc-14968b7b624a@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).