public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Eric Gallager <egallager@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 0ec82f74b170295385f3a1f288e5d371fe5469b9 Date: Tue, 23 Nov 2021 23:50:52 +0000 (GMT) [thread overview] Message-ID: <20211123235052.0A78A3858D28@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 0ec82f74b170295385f3a1f288e5d371fe5469b9 (commit) from ca83c13ad6bf0d351220dafa36264ebc7a6b7816 (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 0ec82f74b170295385f3a1f288e5d371fe5469b9 Author: Eric Gallager <egall@gwmail.gwu.edu> Date: Tue Nov 23 18:50:48 2021 -0500 htdocs/projects/beginner.html: update file extension There are some `.cc` files that include one another diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html index 4ccb5e12..5d055883 100644 --- a/htdocs/projects/beginner.html +++ b/htdocs/projects/beginner.html @@ -129,8 +129,8 @@ still does generate the warning where it's appropriate), we're happy to take those patches too.</p> </li> -<li>Find and expunge all the places where one <code>.c</code> file includes -another. +<li>Find and expunge all the places where one <code>.c</code> (or +<code>.cc</code>) file includes another. <p>In most cases this is just sloppiness, and can easily be converted to separate compilation of both files, then linking the two objects ----------------------------------------------------------------------- Summary of changes: htdocs/projects/beginner.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-11-23 23:50 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=20211123235052.0A78A3858D28@sourceware.org \ --to=egallager@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).