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: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1
Date: Sun, 15 Jan 2017 14:30:00 -0000	[thread overview]
Message-ID: <587b877f.88f2ca0a.12a0a.4292@mx.google.com> (raw)
In-Reply-To: <76298895-b683-5246-ce26-bd9123411990@gmail.com>

On Sun, 15 Jan 2017 09:11:23, cyg Simple wrote:
> It is this expectation that others do the work that you freely use that is the
> problem.

I dont think you realize, I am the maintainer of the Cygwin package manager:

http://github.com/svnpenn/sage

to which I have put hundreds of hours of work into, free of charge. In addition
I donate over a 1,000 commits a year to open source:

http://github.com/svnpenn

And have helped millions of people on Stack Overflow:

http://stackoverflow.com/users/1002260/steven-penny

So please, dont tell me that I am not willing to do open source work. Yes, I do
expect Eric to fix this. readline is a critial Cygwin package and he let a
pretty glaring error get though. It is scary to think what testing he even did
before releasing it. The least he could do is roll it back until the problem has
been fixed by himself or upstream.


--
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:[~2017-01-15 14:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 16:55 Eric Blake (cygwin)
2017-01-13  5:07 ` Steven Penny
2017-01-13 14:47   ` Eric Blake
2017-01-14  0:23     ` Steven Penny
2017-01-14 21:48       ` Eric Blake
2017-01-15  0:27         ` Steven Penny
2017-01-15 13:23           ` Vince Rice
2017-01-15 14:11             ` cyg Simple
2017-01-15 14:30               ` Steven Penny [this message]
2017-01-16 10:32                 ` Yaakov Selkowitz
2017-01-16 12:40                   ` Steven Penny
2017-01-15 22:33         ` Thomas Wolff
2017-01-16  0:45           ` Steven Penny
2017-01-16  0:54             ` Steven Penny
2017-01-17  2:47         ` Steven Penny
2017-01-17  3:32           ` Steven Penny
2017-01-18  0:36             ` Steven Penny
2017-01-18  2:08               ` Eric Blake
2017-01-18  3:55                 ` Steven Penny
2017-01-18  4:09                   ` Doug Henderson
2017-01-18  5:02                     ` Larry Hall (Cygwin)
2017-01-18  5:45                       ` Steven Penny
2017-01-19  5:23                         ` Steven Penny
2017-01-19 13:23                           ` Eliot Moss
2017-01-19 14:21                             ` Eric Blake
2017-01-19 18:13                               ` Corinna Vinschen
2017-01-19 23:54                                 ` Steven Penny
2017-01-20 13:04                                   ` Corinna Vinschen
2017-01-20 14:51                           ` Eric Blake
2017-01-20 15:00                             ` Eric Blake
2017-01-21  3:57                               ` Steven Penny
2017-01-18  1:46     ` Eric Blake

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=587b877f.88f2ca0a.12a0a.4292@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).