Selaa lähdekoodia

Update documentation to refer to new location for issues

Signed-off-by: Stefan Weil <sw@weilnetz.de>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20210619154253.553446-1-sw@weilnetz.de>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Stefan Weil 4 vuotta sitten
vanhempi
commit
e2abbeac7a
2 muutettua tiedostoa jossa 6 lisäystä ja 6 poistoa
  1. 3 3
      .github/lockdown.yml
  2. 3 3
      README.rst

+ 3 - 3
.github/lockdown.yml

@@ -14,11 +14,11 @@ issues:
     at https://gitlab.com/qemu-project/qemu.git.
     at https://gitlab.com/qemu-project/qemu.git.
     The project does not process issues filed on GitHub.
     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:
     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:
 pulls:
   comment: |
   comment: |

+ 3 - 3
README.rst

@@ -131,16 +131,16 @@ will be tagged as my-feature-v2.
 Bug reporting
 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
 found when running code built from QEMU git or upstream released sources
 should be reported via:
 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
 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
 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
 the bug is also known to affect latest upstream code, it can also be
-reported via launchpad.
+reported via GitLab.
 
 
 For additional information on bug reporting consult:
 For additional information on bug reporting consult: