public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: gerald@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. d65a8b4f8d4d625070b3f8cbb07b13dfe1116ae6
Date: Sun, 12 Jan 2020 21:01:00 -0000	[thread overview]
Message-ID: <20200112210116.53444.qmail@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  d65a8b4f8d4d625070b3f8cbb07b13dfe1116ae6 (commit)
      from  8a488efcc0f4265505205aef285ae4a7537ff390 (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 d65a8b4f8d4d625070b3f8cbb07b13dfe1116ae6
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun Jan 12 22:00:38 2020 +0100

    Editorial changes to the AVR news section.
    
    Use "command-line option" over "command line option". Make references
    to older versions of GCC consistent. Improve spelling and grammar.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index c68e00be..caa9df70 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -432,7 +432,7 @@ a work-in-progress.</p>
     has been added.
   </li>
   <li>
-    A new command line option <code>-nodevicespecs</code> has been added.
+    A new command-line option <code>-nodevicespecs</code> has been added.
     It allows to provide a custom device-specs file by means of
     <blockquote><code>
 	avr-gcc -nodevicespecs -specs=<em>my-spec-file</em> &lt;options&gt;
@@ -441,17 +441,17 @@ a work-in-progress.</p>
     <code>-mmcu=</code>.
     See
     <a href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#index-nodevicespecs">AVR
-      command line options</a> for details.
-    This feature is also available in v9.3+ and v8.4+.
+      command-line options</a> for details.
+    This feature is also available in GCC 9.3+ and GCC 8.4+.
   </li>
   <li>
-    New command line options <code>-mdouble=[32,64]</code> and
+    New command-line options <code>-mdouble=[32,64]</code> and
     <code>-mlong-double=[32,64]</code> have been added.  They allow
-    to chose the size (in bits) of the <code>double</code> and
+    to choose the size (in bits) of the <code>double</code> and
     <code>long double</code> types, respectively.  Whether or not the
     mentioned layouts are available, whether the options act
-    as a multilib option, and what is the default for either option
-    is controlled by the new
+    as a multilib option, and the default for either option
+    are controlled by the new
     <a href="https://gcc.gnu.org/install/configure.html#avr">AVR configure
       options</a>
     <code>--with-double=</code> and <code>--with-long-double=</code>.

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

Summary of changes:
 htdocs/gcc-10/changes.html | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-12 21:01 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=20200112210116.53444.qmail@sourceware.org \
    --to=gerald@gcc.gnu.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).