public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/25508] MULTILIB_OSDIRNAMES undocumented
Date: Tue, 23 Dec 2014 17:21:00 -0000 [thread overview]
Message-ID: <bug-25508-4-FDkiWX85PD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-25508-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25508
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The point isn't documenting the rationale for particular choices, it's
documenting (in fragments.texi) the general semantics, including for the
A=B and A=!B forms. It looks like the documentation was added by
r193508 | doko | 2012-11-14 21:29:15 +0000 (Wed, 14 Nov 2012) | 36 lines
but without closing this bug.
next prev parent reply other threads:[~2014-12-23 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25508-4@http.gcc.gnu.org/bugzilla/>
2014-12-22 22:03 ` egall at gwmail dot gwu.edu
2014-12-23 17:21 ` joseph at codesourcery dot com [this message]
2005-12-20 21:31 [Bug other/25508] New: " jsm28 at gcc dot gnu dot org
2005-12-25 1:03 ` [Bug bootstrap/25508] " pinskia 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=bug-25508-4-FDkiWX85PD@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).