From: Eliot Moss <moss@cs.umass.edu>
To: "Hendrickson, Eric D" <edh@optum.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: "Eric @ Gmail" <ericdavidhendrickson@gmail.com>
Subject: Re: Ruby EOL in Cygwin 3.4.9?
Date: Wed, 11 Oct 2023 18:03:22 -0400 [thread overview]
Message-ID: <8cae1a30-cc92-cbea-4599-d7d550850ac5@cs.umass.edu> (raw)
In-Reply-To: <PH7PR22MB31209C697AD372E36AD384ABAFCCA@PH7PR22MB3120.namprd22.prod.outlook.com>
On 10/11/2023 12:37 PM, Hendrickson, Eric D via Cygwin wrote:
> Hello all,
>
> As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here at my place of work. Does anyone know why we are deploying Ruby 2.6 which EOL about 18 months ago?
>
> https://www.ruby-lang.org/en/downloads/branches/
>
> I'm concerned about proliferation of EOL versions of Ruby in case some security risk / 0Day is identified.
>
> Please advise.
> Eric Hendrickson
If nobody has responded I can give a generic response:
"Because cygwin is all volunteer and someone has not volunteered,
or did volunteer and is behind, or fell off the radar."
Someone else will know how to look up if there is a currently
registered volunteer for Ruby ...
Eliot Moss
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
> to which it is addressed. If the reader of this e-mail is not the intended
> recipient or intended recipient’s authorized agent, the reader is hereby
> notified that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.
>
next prev parent reply other threads:[~2023-10-11 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:37 Hendrickson, Eric D
2023-10-11 22:03 ` Eliot Moss [this message]
2023-10-11 22:36 ` Hendrickson, Eric D
2023-10-12 1:11 ` Eliot Moss
2023-10-12 2:55 ` Eric D Hendrickson
2023-10-12 3:59 ` gs-cygwin.com
2023-10-12 4:15 ` Eric D Hendrickson
2023-10-12 4:46 ` gs-cygwin.com
2023-10-12 15:18 ` Eric Hendrickson
2023-10-12 16:53 ` Brian Inglis
2023-10-12 18:21 ` Adam Dinwoodie
2023-10-12 21:46 ` Eric Hendrickson
2023-10-12 22:17 ` David Rothenberger
2023-10-13 9:15 ` Adam Dinwoodie
2023-10-11 22:47 ` Yasuhiro Kimura
2023-10-12 13:42 ` Brian Inglis
2023-10-12 17:43 ` Thomas Schweikle
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=8cae1a30-cc92-cbea-4599-d7d550850ac5@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=edh@optum.com \
--cc=ericdavidhendrickson@gmail.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).