public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request new Ruby release
Date: Sat, 05 May 2018 06:56:00 -0000	[thread overview]
Message-ID: <5aed55ad.13d1370a.52727.af57@mx.google.com> (raw)
In-Reply-To: <e186015e-5a65-20bc-bca0-2a0fb6eda28a@gmail.com>

On Sat, 5 May 2018 07:27:22, Marco Atzeri wrote:
> I am still waiting that you show your code.

i did, here, i can do it again:

http://github.com/svnpenn

> Jon Yong is doing an hell of job taming a monster program,

no one is arguing that, i agree its a tough package to maintain

> and your comments are NOT appropriated.

certainly not by you - and probably others on this list. but my arguments do
have merit. GCC as an example is a fast updating package. and as "politically
incorrect" as it might be, jon could be doing a better job in regards to
velocity of release - at a minimum we should have test versions for GCC 7 and
or 8 already for ALL arches and ALL targets.

> I do not see a huge queue of volunteers,

this is a false assumption - no one volunteers because a maintainer is already
in place - thats like applying for a job that is filled - but if he vacated and
corinna or whatever posted an "opening" - i am confident it would be filled
quickly

> and I do not see your maintaining efforts.

not sure what you mean by this - no i havent maintained an official cygwin
package - but i maintain several public facing cygwin packages:

http://github.com/svnpenn/glade

along with a Cygwin package manager:

http://github.com/svnpenn/sage

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


--
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:[~2018-05-05  6:56 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 [this message]
2018-05-05 16:18               ` Stephen John Smoogen
2018-05-06  5:54               ` Yaakov Selkowitz
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=5aed55ad.13d1370a.52727.af57@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).