From: Sandra Loosemore <sandra@codesourcery.com>
To: Jeff Law <law@redhat.com>
Cc: FX <fxcoudert@gmail.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch,doc] Remove dead/inactive links for GCC binaries
Date: Mon, 24 Aug 2015 19:28:00 -0000 [thread overview]
Message-ID: <55DB6C11.7080705@codesourcery.com> (raw)
In-Reply-To: <55DB54E3.3040804@redhat.com>
On 08/24/2015 11:31 AM, Jeff Law wrote:
> On 08/22/2015 01:01 AM, FX wrote:
>> Attached patch cleans up the list of links we provide for GCC binaries:
>>
>> - pware.hvcc.edu is dead, no mirror or newer alternative found
>> - h8300-hms.sourceforge.net is inactive since 2003, carries only gcc
>> 3.2 and 3.3
>> - sunsite.informatik.rwth-aachen.de only has gcc 3.0.1
>> - SCO website has gcc 2.95.2
>> - ftp.thewrittenword.com only offers gcc 4.0.2
>>
>> Tested with "make pdf info html", OK to commit?
> One could argue all this ought to go away, but no reason to hold up your
> cleanup. So this is fine for the trunk.
Heh, I was about to suggest just deleting the whole section, too. I
think nowadays most people get native GCC from their OS distro and cross
toolchains for embedded targets from their hardware vendor or consortium
(e.g., Linaro). And, well, there's Google if you need help finding a
GCC for your target....
That said, I think removing broken or unuseful links from the
documentation qualifies as an "obvious" fix, if folks think the
remaining information in the section is actually useful.
-Sandra
next prev parent reply other threads:[~2015-08-24 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 8:02 FX
2015-08-24 17:41 ` Jeff Law
2015-08-24 19:28 ` Sandra Loosemore [this message]
2015-08-24 21:03 ` FX
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=55DB6C11.7080705@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
/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).