From: Jivan Hakobyan <jivanhakobyan9@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: Jeff Law <jlaw@ventanamicro.com>
Subject: [wwwdocs] Broken URL to README in st/cli-be project
Date: Thu, 15 Jun 2023 00:54:16 +0400 [thread overview]
Message-ID: <CAHso6sMOUUaacFk0bBSudP51=s3scoYs87AWu4WZMk52LOym2Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 129 bytes --]
In CLI project link to README is broken. This patch fixes that.
Discussed in PR110250
--
With the best regards
Jivan Hakobyan
[-- Attachment #2: cli.diff --]
[-- Type: text/x-patch, Size: 550 bytes --]
diff --git a/htdocs/projects/cli.html b/htdocs/projects/cli.html
index 380fb031..394832b6 100644
--- a/htdocs/projects/cli.html
+++ b/htdocs/projects/cli.html
@@ -145,7 +145,7 @@ are followed.
</p>
<p>There is a small
-<a href="https://gcc.gnu.org/svn/gcc/branches/st/README?view=markup">README
+<a href="https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=README;hb=refs/vendors/st/heads/README">README
file</a> that explains how to build and install the GCC CLI back end and
front end and the CLI binutils (both Mono based and DotGnu based) .
</p>
next reply other threads:[~2023-06-14 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 20:54 Jivan Hakobyan [this message]
2023-06-17 18:05 ` Jeff Law
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='CAHso6sMOUUaacFk0bBSudP51=s3scoYs87AWu4WZMk52LOym2Q@mail.gmail.com' \
--to=jivanhakobyan9@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
/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).