public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 825e08cc639eb27289f8700431438d0909be10dc Date: Tue, 12 Apr 2022 09:16:44 +0000 (GMT) [thread overview] Message-ID: <20220412091644.F2C753858C56@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 825e08cc639eb27289f8700431438d0909be10dc (commit) from 3ef70e31b37efaa93cff05c4c9175e15f6bdd7aa (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 825e08cc639eb27289f8700431438d0909be10dc Author: Arnaud Charlet <charlet@adacore.com> Date: Tue Apr 12 09:16:36 2022 +0000 Fix typo diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 3c7a3649..4652304d 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -227,7 +227,7 @@ a work-in-progress.</p> records and arrays as well as finer grained casing on scalar types. In the future it is expected to provide more compile time guarantees when accessing discriminated fields. Case - exhaustion is supported for patter matching. An example would + exhaustion is supported for pattern matching. An example would be <code><pre> type Sign is (Neg, Zero, Pos); ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-04-12 9:16 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=20220412091644.F2C753858C56@sourceware.org \ --to=charlet@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).