public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/31355] --help=<language> option isn't documented.
Date: Thu, 29 Mar 2007 10:08:00 -0000	[thread overview]
Message-ID: <20070329100823.31562.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31355-13350@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from nickc at redhat dot com  2007-03-29 11:08 -------
Subject: Re:  --help=<language> option isn't documented.

Hi Brooks,

> The patch tracker missed the patch I'd already posted for this one as well:
> http://gcc.gnu.org/ml/gcc-patches/2007-03/msg01655.html
> 
> I think our fixes are fairly equivalent here; yours specifies the list of
> language, whereas mine uses @var{language} -- which I think is slightly better,
> because the list of languages isn't necessarily fixed (and you missed obj-c++),
> though I could see yours as being slightly clearer.  However, note that my
> patch includes some formatting fixes to this section, which should be
> incorporated regardless.

Agreed, your patch is superior to mine.

> (Note, by the way, that the small problem you mention in --help=<language>
> output is Bug #31356.  :) )

:-)

Cheers
   Nick


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31355


  parent reply	other threads:[~2007-03-29 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 22:24 [Bug other/31355] New: " brooks at gcc dot gnu dot org
2007-03-25 22:34 ` [Bug driver/31355] " pinskia at gcc dot gnu dot org
2007-03-28 12:40 ` nickc at redhat dot com
2007-03-28 18:23 ` brooks at gcc dot gnu dot org
2007-03-29 10:08 ` nickc at redhat dot com [this message]
2007-04-04 18:32 ` brooks at gcc dot gnu dot org

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=20070329100823.31562.qmail@sourceware.org \
    --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).