public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 61292da053c09f9c1725e4a7ca59871a76893e13 Date: Sat, 2 Apr 2022 14:13:46 +0000 (GMT) [thread overview] Message-ID: <20220402141346.D64F7383943C@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 61292da053c09f9c1725e4a7ca59871a76893e13 (commit) from 729cfc5c9e0070f04731ea593911fb485b1525a6 (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 61292da053c09f9c1725e4a7ca59871a76893e13 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sat Apr 2 16:13:05 2022 +0200 gcc-4.3: Update fedora-devel-list archives link diff --git a/htdocs/gcc-4.3/porting_to.html b/htdocs/gcc-4.3/porting_to.html index 630290ce..5301729f 100644 --- a/htdocs/gcc-4.3/porting_to.html +++ b/htdocs/gcc-4.3/porting_to.html @@ -527,7 +527,7 @@ svn diff -r529854:529855 http://svn.apache.org/repos/asf/ant/core/trunk/src/main <p> Jakub Jelinek, -<a href="https://listman.redhat.com/archives/fedora-devel-list/2008-January/msg00128.html"> +<a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/WV3KUDEP2JNOWGWES42RQZFYFNLFLAMJ/"> Mass rebuild status with gcc-4.3.0-0.4 of rawhide-20071220</a> </p> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-4.3/porting_to.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-04-02 14:13 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=20220402141346.D64F7383943C@sourceware.org \ --to=gerald@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).