public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: burnus@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6cbb3cad933899c6d940436196e7ccb6bf154896 Date: Tue, 03 Dec 2019 08:52:00 -0000 [thread overview] Message-ID: <20191203085233.9692.qmail@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1551 bytes --] 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 6cbb3cad933899c6d940436196e7ccb6bf154896 (commit) from 67aae10548db6f5014afc6dca06bc98acdcc66df (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 6cbb3cad933899c6d940436196e7ccb6bf154896 Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue Dec 3 09:52:02 2019 +0100 Fix example code in porting to * htdocs/gcc-10/porting_to.html: Remove duplicated example code. diff --git a/htdocs/gcc-10/porting_to.html b/htdocs/gcc-10/porting_to.html index 35df91d..3256e8a 100644 --- a/htdocs/gcc-10/porting_to.html +++ b/htdocs/gcc-10/porting_to.html @@ -113,7 +113,7 @@ longer compile it.) real var real <span class="red">var2(1)</span> ⦠- <span class="red">var2(1)</span>var2(1) = var + <span class="red">var2(1)</span> = var call sub_assumed(var<span class="red">2</span>, 1) <span class="red">var = var2(1)</span> end ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/porting_to.html | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2019-12-03 8:52 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=20191203085233.9692.qmail@sourceware.org \ --to=burnus@gcc.gnu.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).