public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Request new Ruby release
Date: Sun, 06 May 2018 05:54:00 -0000	[thread overview]
Message-ID: <f0686fb3-b90c-fc8a-9947-6317ea674d55@cygwin.com> (raw)
In-Reply-To: <5aed55ad.13d1370a.52727.af57@mx.google.com>

On 2018-05-05 01:56, Steven Penny wrote:
> On Sat, 5 May 2018 07:27:22, Marco Atzeri wrote:
>> Jon Yong is doing an hell of job taming a monster program,
>> and your comments are NOT appropriated.
> 
> certainly not by you - and probably others on this list.

The question is, if you actually understand your comments are not
appreciated, why do you insist on making them anyway?

> GCC as an example is a fast updating package.

No, not really.

> and as "politically incorrect" as it might be, jon could be doing a
> better job in regards to velocity of release 

Jon is doing just fine, and has our full confidence and backing.  We
simply don't have the manpower of large distributions to deal with the
consequences of potential compiler bugs, so we tend to aim for X.3.0.

> at a minimum we should have test versions for GCC 7 and or 8 already 

https://cygwin.com/ml/cygwin-announce/2018-04/msg00034.html
https://cygwin.com/ml/cygwin-announce/2018-05/msg00002.html

> for ALL arches and ALL targets.

Jon does not maintain all of the cross-compilers, and as he already
stated earlier, the native GCC 7 is a prerequisite to the MinGW GCC 7
because GNAT is written in Ada.

As for the aforementioned cygwin*-gcc, those are 32<->64 bit
cross-compilers.  I dropped Ada from those because there really isn't a
use for it since the original 64-bit bootstrapping.

>> and I do not see your maintaining efforts.
> 
> not sure what you mean by this - no i havent maintained an official cygwin
> package

Exactly.  Griping (or worse) at those who are actually doing the work
while you contribute nothing doesn't get you very far.  Perhaps the
following will help you gain some perspective:

Almost 10 years ago, I was the one being similarly targeted, and an
"older" (at least wrt Cygwin), now former, contributor to Cygwin
rightfully came to my defence in epic fashion:

https://cygwin.com/ml/cygwin-xfree/2008-11/msg00242.html

I have never forgotten that, and hence am prepared to similarly defend
my fellow contributors (albeit probably not as eloquently).

>> This only show how ignorant you are about programming language and
>> their usage. Clearly you are not an engineer.
> 
> id say the same to you - as you seen keen on throwing insults rather
> than links and examples - cheers.

You are the one who insists on throwing insults time and again, and I
have warned you about your tone before.  I suggest you take heed.

-- 
Yaakov

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

  parent reply	other threads:[~2018-05-06  5:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 20:51 Steven Penny
2018-05-03 23:17 ` Steven Penny
2018-05-04  3:09   ` Yaakov Selkowitz
2018-05-04  6:05   ` Brian Inglis
2018-05-04 12:09     ` Steven Penny
2018-05-04 13:16       ` Marco Atzeri
2018-05-05  0:57         ` Steven Penny
2018-05-05  3:41           ` Brian Inglis
2018-05-05  5:27           ` Marco Atzeri
2018-05-05  6:56             ` Steven Penny
2018-05-05 16:18               ` Stephen John Smoogen
2018-05-06  5:54               ` Yaakov Selkowitz [this message]
2018-05-06 14:08                 ` Steven Penny
2018-05-14 16:10                   ` cyg Simple
2018-05-15  4:17                     ` Steven Penny
2018-05-15 13:27                       ` What is Cygwin and MinGW [WAS: Request new Ruby release] cyg Simple
2018-05-15 14:37                       ` Request new Ruby release Adam Dinwoodie

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=f0686fb3-b90c-fc8a-9947-6317ea674d55@cygwin.com \
    --to=yselkowitz@cygwin.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).