public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. e48038c3f56ea858222f79162c74e858886f572d Date: Sat, 17 Jun 2023 18:05:06 +0000 (GMT) [thread overview] Message-ID: <20230617180506.1731F3858D35@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via e48038c3f56ea858222f79162c74e858886f572d (commit) from f6bf76c21963f965ed46faa8dca49f6666481099 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit e48038c3f56ea858222f79162c74e858886f572d Author: Jivan Hakobyan <jivanhakobyan9@gmail.com> Date: Sat Jun 17 12:04:43 2023 -0600 Fix broken URL to README in st/cli-be project. 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> ----------------------------------------------------------------------- Summary of changes: htdocs/projects/cli.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-06-17 18:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230617180506.1731F3858D35@sourceware.org \ --to=law@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).