CVS commit: pkgsrc/doc/guide/files

["Dan Cirnat" <cirnatdan%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   cirnatdan
Date:           Tue Apr 13 11:01:17 UTC 2021

Modified Files:
        pkgsrc/doc/guide/files: gnome.xml

Log Message:
doc: GNOME and freedesktop.org GitLab links

GNOME and freedesktop.org no longer use Bugzilla for issue tracking.
Both projects switched to Git and GitLab for development.


To generate a diff of this commit:
cvs rdiff -u -r1.11 -r1.12 pkgsrc/doc/guide/files/gnome.xml

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/doc/guide/files/gnome.xml
diff -u pkgsrc/doc/guide/files/gnome.xml:1.11 pkgsrc/doc/guide/files/gnome.xml:1.12
--- pkgsrc/doc/guide/files/gnome.xml:1.11       Mon Feb 24 21:13:56 2020
+++ pkgsrc/doc/guide/files/gnome.xml    Tue Apr 13 11:01:17 2021
@@ -1,4 +1,4 @@
-<!-- $NetBSD: gnome.xml,v 1.11 2020/02/24 21:13:56 rillig Exp $ -->
+<!-- $NetBSD: gnome.xml,v 1.12 2021/04/13 11:01:17 cirnatdan Exp $ -->
 
 <chapter id="gnome"> <?dbhtml filename="gnome.html"?>
 <title>GNOME packaging and porting</title>
@@ -355,14 +355,14 @@ pkgsrc, the easier further updates are. 
 issuing major GNOME updates will be grateful if you do that.</para>
 
 <para>The most common places to report bugs are the <ulink
-url="https://bugzilla.gnome.org/";>GNOME's Bugzilla</ulink> and the <ulink
-url="https://bugzilla.freedesktop.org/";>freedesktop.org's
-Bugzilla</ulink>.  Not all components use these to track bugs, but most
+url="https://gitlab.gnome.org/GNOME";>GNOME's GitLab</ulink> and the <ulink
+url="https://gitlab.freedesktop.org/explore/groups";>freedesktop.org's
+GitLab</ulink>.  Not all components use these to track bugs, but most
 of them do.  Do not be short on your reports: always provide detailed
 explanations of the current failure, how it can be improved to achieve
-maximum portability and, if at all possible, provide a patch against CVS
-head.  The more verbose you are, the higher chances of your patch being
-accepted.</para>
+maximum portability and, if at all possible, provide a patch against the
+main Git branch.  The more verbose you are, the higher chances of your
+patch being accepted.</para>
 
 <para>Also, please avoid using preprocessor magic to fix portability
 issues.  While the FreeBSD GNOME people are doing a great job in porting