public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/106638] docs: bad links to DIPs
Date: Tue, 16 Aug 2022 11:23:22 +0000	[thread overview]
Message-ID: <bug-106638-4-jQ5f7gMB4G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106638-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106638

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Iain Buclaw
<ibuclaw@gcc.gnu.org>:

https://gcc.gnu.org/g:f6431df36461ba88f462b153fb21f6ca7497a30a

commit r12-8691-gf6431df36461ba88f462b153fb21f6ca7497a30a
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Tue Aug 16 12:22:10 2022 +0200

    d: Update DIP links in gdc documentation to point at upstream repository

    The wiki links probably worked at some point in the distant past, but
    now the official location of tracking all D Improvement Proposals is on
    the upstream dlang/DIPs GitHub repository.

            PR d/106638

    gcc/d/ChangeLog:

            * gdc.texi: Update DIP links to point at upstream dlang/DIPs
            repository.

    (cherry picked from commit e56b695aa3aed3c0c80616bba569bbeb4a06b5e5)

  parent reply	other threads:[~2022-08-16 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  8:03 [Bug d/106638] New: " marxin at gcc dot gnu.org
2022-08-16  8:04 ` [Bug d/106638] " marxin at gcc dot gnu.org
2022-08-16 10:20 ` ibuclaw at gdcproject dot org
2022-08-16 10:25 ` cvs-commit at gcc dot gnu.org
2022-08-16 11:23 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-16 11:31 ` cvs-commit at gcc dot gnu.org
2022-08-16 11:32 ` cvs-commit at gcc dot gnu.org
2022-08-16 11:33 ` ibuclaw at gdcproject dot org

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=bug-106638-4-jQ5f7gMB4G@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).