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. b950936b1f8fc71eba7d7c6a220ab1b7cabc5ed3 Date: Wed, 14 Feb 2024 00:37:56 +0000 (GMT) [thread overview] Message-ID: <20240214003756.865323857C5B@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 b950936b1f8fc71eba7d7c6a220ab1b7cabc5ed3 (commit) from 0d342ea1855ae767f85c7b9dad6e5d9148a7833a (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 b950936b1f8fc71eba7d7c6a220ab1b7cabc5ed3 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Wed Feb 14 01:37:25 2024 +0100 gcc-14: Fix typo in AVR section diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 6ac7c8b1..92bd0a7b 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -370,7 +370,7 @@ a work-in-progress.</p> precedence over <code>__flmap</code>. For example, linking with <nobr><code>-Wl,--defsym,__RODATA_FLASH_START__=32k</code></nobr> - choses the second 32 KiB block.</li> + chooses the second 32 KiB block.</li> <li>The default uses the last 32 KiB block, which is also the hardware default for bit-field <code>NVMCTRL_CTRLB.FLMAP</code>.</li> <li>When a non-default block is used, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-02-14 0:37 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=20240214003756.865323857C5B@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: 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).