public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: gcc-9.2.0-1 (x86/x86_64) (Testing)
Date: Fri, 07 Feb 2020 02:27:00 -0000	[thread overview]
Message-ID: <5e3ccb09.1c69fb81.a29f4.43ab@mx.google.com> (raw)
In-Reply-To: <0216baa3-a6b4-839b-a678-cdf4e9c3f7b7@gmail.com>

On Thu, 6 Feb 2020 08:16:12 +0000, JonY wrote:
> I normally don't update mingw-w64 compilers unless the cygwin gcc has
> stabilized.
> 
> Do you need it ASAP? I can work on it soon if required.

I mean isnt that the whole point of Test packages? The way I see it the Test
package should always be matching the major version, and ideally the minor
version.

For even the test version to be literally 2 majors versions back kills any
reason to even have it. It would be better to just remove the test version
altogether and just have current and "prev" if it cant be kept up to date.
On a personal note the optics just look bad. GCC points people to Cygwin:

https://gcc.gnu.org/install/binaries.html

then when the users get here, they find the mingw64-x86_64-gcc-core 7.3 which
is 2 years old:

https://gcc.gnu.org/releases.html


--
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

      reply	other threads:[~2020-02-07  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 13:50 JonY
2020-02-01 18:35 ` Steven Penny
2020-02-06  8:16   ` JonY
2020-02-07  2:27     ` Steven Penny [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=5e3ccb09.1c69fb81.a29f4.43ab@mx.google.com \
    --to=svnpenn@gmail.com \
    --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).