public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/68043] many undocumented options, missing punctuation
Date: Thu, 22 Oct 2015 23:48:00 -0000	[thread overview]
Message-ID: <bug-68043-4-9iKm6Xc3wz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68043-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68043

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Thu Oct 22 23:48:17 2015
New Revision: 229205

URL: https://gcc.gnu.org/viewcvs?rev=229205&root=gcc&view=rev
Log:
gcc/ChangeLog:

2015-10-22  Martin Sebor  <msebor@redhat.com>

        PR driver/68043
        * config/i386/i386.opt: Add missing periods to the ends of sentences.
        * config/msp430/msp430.opt: Same.

gcc/testsuite/ChangeLog:

2015-10-22  Martin Sebor  <msebor@redhat.com>

        PR driver/68043
        * gcc.misc-tests/help.exp: Verify that option descriptions
        end in periods.
        * lib/options.exp (check_for_options): Use the regexp --line option.
        Print unexpected match on failure.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.opt
    trunk/gcc/config/msp430/msp430.opt
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.misc-tests/help.exp
    trunk/gcc/testsuite/lib/options.exp


      parent reply	other threads:[~2015-10-22 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-68043-4@http.gcc.gnu.org/bugzilla/>
2015-10-21 20:22 ` msebor at gcc dot gnu.org
2015-10-21 22:27 ` msebor at gcc dot gnu.org
2015-10-22 23:48 ` msebor at gcc dot gnu.org [this message]

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=bug-68043-4-9iKm6Xc3wz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).