[gimp-web] content: deleted /bugs/howtos/submit-patch.html page.

[Jehan <jehanp src gnome org>]

commit 87731caa56e7b6136be72238b4023ff5f17535ab
Author: Jehan <jehan girinstud io>
Date:   Wed Sep 21 20:42:59 2022 +0200

    content: deleted /bugs/howtos/submit-patch.html page.
    
    For everything development related, the new developer website will be the new
    reference. It now contains a nice up-to-date tutorial which will be available in
    https://developer.gimp.org/core/submit-patch/ (not available yet, but will be
    when we will finally publish the new developer website, which we will sync with
    the next wgo merge).
    
    Note that most of the contents in wgo's submit-patch page has been reused in the
    developer website equivalent page. Some info are not there, when they are
    basically outdated procedures or advices.
    We also do not copy the section about making a patch against the latest release.
    Nowadays asking developers to use the "HEAD" of the relevant git branch is the
    standard, and patches made against a tarball are very rare. The only ones we see
    these days are mostly by packagers who know how to make such patches.

 content/about/meta/file-list.md     |  2 +-
 content/bugs/howtos/submit-patch.md | 94 -------------------------------------
 content/bugs/index.md               |  6 +--
 3 files changed, 4 insertions(+), 98 deletions(-)
---
diff --git a/content/about/meta/file-list.md b/content/about/meta/file-list.md
index 1d6f20fb..53716256 100644
--- a/content/about/meta/file-list.md
+++ b/content/about/meta/file-list.md
@@ -48,7 +48,7 @@ The main page links go to legacy WGO, the link icon (if there) will go to the po
 <del><http://www.gimp.org/bugs/why_bugzilla.html></del> [<i class="fa 
fa-link"></i>]({filename}../../bugs/why_bugzilla.md) (redirected to [/bugs/report.html](/bugs/report.html))  
 <del><http://www.gimp.org/bugs/howtos/bugzilla.html></del> [<i class="fa 
fa-link"></i>]({filename}../../bugs/howtos/bugzilla.md) (redirected to 
[/bugs/report.html](/bugs/report.html))  
 <del><http://www.gimp.org/bugs/howtos/howto-template.html></del> (skipping - test/placeholder data)  
-<del><http://www.gimp.org/bugs/howtos/submit-patch.html></del> [<i class="fa 
fa-link"></i>]({filename}../../bugs/howtos/submit-patch.md)  
+<del><http://www.gimp.org/bugs/howtos/submit-patch.html></del> [<i class="fa 
fa-link"></i>]({filename}../../bugs/howtos/submit-patch.md) (redirected to 
[developer.gimp.org/core/submit-patch/](https://developer.gimp.org/core/submit-patch/)
 
 <http://www.gimp.org/contest/index.html>  (deprecated - not keeping this URI?)  
 
diff --git a/content/bugs/index.md b/content/bugs/index.md
index 8d1a37d2..49d1d716 100644
--- a/content/bugs/index.md
+++ b/content/bugs/index.md
@@ -81,9 +81,9 @@ report an issue in GIMP Website
 Otherwise please read our tutorial: [How To Report an Issue]({filename}report.md)
 
 ℹ️  Note that if you are looking for fixing the problem yourself, you might
-rather be interested by our [🧑‍💻 developer
-website](https://testing.developer.gimp.org/core/), which contains tutorials on
-how to build GIMP and submit your first patch.
+rather be interested by our [tutorial on the 🧑‍💻 developer
+website](https://developer.gimp.org/core/submit-patch/), on how to submit your
+first patch.
 
 ## Enhancing Bug Reports