public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 60dfe344b601a225cf477da1720517872175dd1a
Date: Mon, 19 Feb 2024 20:00:50 +0000 (GMT)	[thread overview]
Message-ID: <20240219200050.C8ED73858D33@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  60dfe344b601a225cf477da1720517872175dd1a (commit)
      from  4a56e1431bd0e2e3d435168216d7beec462b004a (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 60dfe344b601a225cf477da1720517872175dd1a
Author: Florian Weimer <fweimer@redhat.com>
Date:   Mon Feb 19 20:59:43 2024 +0100

    gcc-14: Fix unintentional error in -Wimplicit-int example

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index bbbaa25a..901a1653 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -92,7 +92,7 @@ below).  In the example below, the type of <code>s</code> should be
 <pre>
   write_string (fd, s)
   {
-    write (1, s, strlen (s));
+    write (fd, s, strlen (s));
   }
 </pre>
 
@@ -103,7 +103,7 @@ disregarding error handling and short writes):
   <ins>void</ins>
   write_string (<ins>int</ins> fd, <ins>const char *</ins>s)
   {
-    write (1, s, strlen (s));
+    write (fd, s, strlen (s));
   }
 </pre>
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-14/porting_to.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-02-19 20:00 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=20240219200050.C8ED73858D33@sourceware.org \
    --to=fw@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: 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).