From: Gerald Pfeifer <gerald@pfeifer.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc-patches@gcc.gnu.org,
Eric Weddington <eric.weddington@atmel.com>,
Denis Chertykov <chertykov@gmail.com>
Subject: Re: [Patch,wwwdocs,AVR]: AVR release notes
Date: Sat, 11 Apr 2015 00:02:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504110201070.9357@tuna.site> (raw)
In-Reply-To: <4F3BE5AC.5090904@gjlay.de>
On Wed, 15 Feb 2012, Georg-Johann Lay wrote:
> Georg-Johann Lay wrote:
>
>> http://gcc.gnu.org/gcc-4.7/changes.html
>>
>> But there is a problem with the link to built-ins in onlinedocs.
>>
>> The HTML reads
>>
>> <li>Support for AVR-specific <a
>> href="http://gcc.gnu.org/onlinedocs/gcc/AVR-Built_002din-Functions.html">built-in
>> functions</a> has been added.</li>
>>
>> But that is not used literally but as
>> "http://gcc.gnu.org/onlinedocs/gcc/AVR-Built-in-Functions.html"
>> instead leading to 404 "Not found" error.
>>
>> It _002d link works from by local sandbox but not from the upstream version.
>>
>> What is the trick?
> Hacked around it by escaping _002d as %5f002d so that _002d is not
> resolved to -
None of this should be necessary (and should not have been for
18 months or so), finally. :-) If you still run into anything,
please let me know and I'll look into it.
Gerald
prev parent reply other threads:[~2015-04-11 0:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:30 Georg-Johann Lay
2012-01-25 15:57 ` Ping #1: " Georg-Johann Lay
2012-01-29 23:27 ` Gerald Pfeifer
2012-01-30 13:55 ` Georg-Johann Lay
2012-01-30 18:59 ` Weddington, Eric
2012-01-30 23:07 ` Georg-Johann Lay
2012-02-12 22:23 ` Gerald Pfeifer
2012-02-13 14:28 ` Weddington, Eric
2012-02-15 17:04 ` Georg-Johann Lay
2012-02-15 17:17 ` Georg-Johann Lay
2015-04-11 0:02 ` Gerald Pfeifer [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=alpine.LSU.2.20.1504110201070.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=avr@gjlay.de \
--cc=chertykov@gmail.com \
--cc=eric.weddington@atmel.com \
--cc=gcc-patches@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).