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. 8137d37b26794c5bcad139423abddcd105a33780
Date: Fri, 14 Apr 2023 21:48:47 +0000 (GMT)	[thread overview]
Message-ID: <20230414214847.6A6E13858C5E@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  8137d37b26794c5bcad139423abddcd105a33780 (commit)
      from  c47107cdfdb6c5c9e7e82fd8336f84386a823b27 (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 8137d37b26794c5bcad139423abddcd105a33780
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri Apr 14 23:39:47 2023 +0200

    codingconventions: Recommend "file name" over "filename"
    
    This aligns with the C and C++ standards as well as the GNU Coding
    Standards, though POSIX uses "filename" as a component of "pathname".

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 8b3cb8bb..9b6d243d 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -469,6 +469,11 @@ and code.  The following table lists some simple cases:</p>
     <td>"run time" or "runtime"</td>
     <td></td>
   </tr>
+  <tr>
+    <td>file name</td>
+    <td>filename</td>
+    <td></td>
+  </tr>
   <tr>
     <td>"floating-point" (adjective)</td>
     <td>"floating point"</td>

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

Summary of changes:
 htdocs/codingconventions.html | 5 +++++
 1 file changed, 5 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-04-14 21:48 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=20230414214847.6A6E13858C5E@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: 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).