public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. e53da9d37d4a1c998e52abdf02f39558088d123d
Date: Sat,  4 Feb 2023 20:25:34 +0000 (GMT)	[thread overview]
Message-ID: <> (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  e53da9d37d4a1c998e52abdf02f39558088d123d (commit)
      from  5256cf5d726fdda76956197f9834ca765bac26a9 (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 e53da9d37d4a1c998e52abdf02f39558088d123d
Author: Gerald Pfeifer <>
Date:   Sat Feb 4 21:24:58 2023 +0100

    projects/beginner: Remove traces of Interix

diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html
index 0cefb562..83efbd86 100644
--- a/htdocs/projects/beginner.html
+++ b/htdocs/projects/beginner.html
@@ -718,9 +718,7 @@ them is in six categories:</p>
   <li><p>Things that belong in a <code>tm.h</code> or
       <code>t-<var>target</var></code> file.  E.g. <code>x-linux</code>
-      has no business saying not to run fixproto,
-      <code>xm-interix.h</code> has no business specifying how to run
-      global constructors.</p></li>
+      has no business saying not to run fixproto.</p></li>
   <li><p>System category assertions, which should be replaced by feature
       checks, but we have to do work in machine-independent code


Summary of changes:
 htdocs/projects/beginner.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)


                 reply	other threads:[~2023-02-04 20:25 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).