public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/52382] Atomic builtins documentation, page not found
Date: Mon, 27 Feb 2012 14:14:00 -0000 [thread overview]
Message-ID: <bug-52382-4-ogSKYT36fd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52382-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52382
Andrew Macleod <amacleod at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bkoz at gcc dot gnu.org
--- Comment #4 from Andrew Macleod <amacleod at redhat dot com> 2012-02-27 14:12:57 UTC ---
Wonder why the names changed? I didn't actually add that link.
I would think the sync legacy page ought to have the same name it use to (ie,
rename the texinfo node, which I have no idea how to do) because who knows how
many links to that are floating around.
The new atomics didnt exist before now, so there shouldn't be many links to
them... Id be tempted to just use the current name since I presume it was
changed for a reason... I'm guessing bkoz knows how or why the names are
different now? Or maybe there wasn't a good reason for the texinfo node name
change.
prev parent reply other threads:[~2012-02-27 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 17:34 [Bug c/52382] New: " mib.bugzilla at gmail dot com
2012-02-25 17:37 ` [Bug web/52382] " redi at gcc dot gnu.org
2012-02-25 18:57 ` redi at gcc dot gnu.org
2012-02-25 20:02 ` pinskia at gcc dot gnu.org
2012-02-27 9:25 ` rguenth at gcc dot gnu.org
2012-02-27 14:14 ` amacleod at redhat dot com [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-52382-4-ogSKYT36fd@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).