From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: gcc-4.7.3-1
Date: Tue, 02 Jul 2013 15:02:00 -0000 [thread overview]
Message-ID: <51D2EBA6.1070407@cs.utoronto.ca> (raw)
In-Reply-To: <51D2E8AC.1040902@gmail.com>
On 02/07/2013 10:50 AM, JonY wrote:
> On 7/2/2013 20:00, Ryan Johnson wrote:
>> On 02/07/2013 6:26 AM, JonY wrote:
>>> Version 4.7.3-1 of gcc has been uploaded. Some important notes are:
>>>
>>> * gcc-3.x is now finally removed, replaced by this version.
>>>
>>> * This means -mno-cygwin support is also removed completely, use the
>>> provided cross compilers to build Windows code.
>>>
>>> * Previous gcc4-4.5.3 has been renamed to gcc and placed as previous.
>> So this means there is now only one gcc package now, called "gcc" ? With
>> 4.7.3 being the current/default version and 4.5.3 being available as the
>> "previous" version in setup if you insist on using old stuff?
>>
>> How delightful!
> Yes, it is finally gone :)
>
> I wonder when the backlash from users following outdated guides and FAQs
> will start.
You know, we should really have some sort of bounty program where people
can bring up third-party "stuff" and have it added to a list in cygwin's
web page somewhere: if it covers something useful (as in, cygwin's
documentation was lacking), we can incorporate the goodness with proper
attribution; if it's out of date or just plain inaccurate, we can flag
it as such. Knowing how Google works, it's entirely plausible that
somebody searching for an outdated guide would instead find Cygwin's
link to it, along with the blurb explaining why it shouldn't be used
[1]. It would be especially delicious if some of those sites had
automatic track-back systems that posted the official cygwin take in
their own comments. It would also encourage people to check the source
first (or at least check that list) before swallowing a cygwin myth,
kind of like snopes does for internet hoaxes.
Of course, SHTDI, so this may never happen... but it might cut list
traffic enough to pay for itself.
Ryan
[1] We could call it "Embrace, Embarrass, Eliminate." Microsoft would be
proud.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-07-02 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 11:29 JonY
2013-07-02 11:55 ` Eric Lilja
2013-07-02 12:00 ` Ryan Johnson
2013-07-02 14:50 ` JonY
2013-07-02 15:02 ` Ryan Johnson [this message]
2013-07-02 13:19 ` Csaba Raduly
2013-12-17 16:05 ` Trong Nguyen
2013-12-17 17:04 ` marco atzeri
2013-12-21 1:51 ` Reini Urban
2013-12-21 14:36 ` Achim Gratz
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=51D2EBA6.1070407@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.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).