public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Chris J. Breisch" <chris.ml@breisch.org>
To: cygwin@cygwin.com
Subject: Re: Update CoreUtils
Date: Tue, 13 May 2014 18:47:00 -0000	[thread overview]
Message-ID: <53726637.8040301@breisch.org> (raw)
In-Reply-To: <CAAXzdLXO3moCP_nPkwReqkW0e=eU9pjT+XsC0Ys5+=ib-NZmaw@mail.gmail.com>

Steven Penny wrote:
> On Tue, May 13, 2014 at 10:04 AM, Christopher Faylor wrote:
>> Funny how you're saying "We" as if you are actually contributing
>> anything other than criticism.
>
> You want me to contribute? Give me maintenance over one of the aforementioned
> packages. Ball is in your court.
>
If you're ready to maintain something, then you must have successfully 
built the version of the package you want to maintain, applied any 
necessary Cygwin patches, and gotten it to successfully work on your 
machine.

Since you've done all that, I am touched by your concern that the rest 
of us are running out-of-date stuff, and am glad that you are so eager 
to contribute. I'm sure Eric et al. would be happy to accept the 
assistance. PTC. (http://cygwin.com/acronyms/#PTC)

Of course, if you haven't yet successfully built the version of the 
package you want to maintain, haven't applied the necessary Cygwin 
patches, and haven't gotten it to successfully work on your machine, 
then it's a bit ludicrous to expect someone to name you the maintainer 
of said package. You haven't shown any evidence of your ability to 
perform in that capacity.



-- 
Chris J. Breisch

--
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:[~2014-05-13 18:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 16:42 Steven Penny
2014-05-11 19:10 ` Thomas Wolff
2014-05-12 14:57   ` Eric Blake
2014-05-12 14:53 ` Eric Blake
2014-05-12 22:01   ` Steven Penny
2014-05-13  8:29     ` Christopher Faylor
2014-05-13 12:46       ` Steven Penny
2014-05-13 13:09         ` Peter Rosin
2014-05-13 15:04           ` Steven Penny
2014-05-13 15:05             ` Christopher Faylor
2014-05-13 18:36               ` Steven Penny
2014-05-13 18:47                 ` Chris J. Breisch [this message]
2014-05-13 18:52                   ` Larry Hall (Cygwin)
2014-05-13 19:16                     ` Eric Blake
2014-05-13 21:11                   ` Steven Penny
2014-05-13 19:43                 ` Christopher Faylor
2014-05-13 23:26                   ` Christopher Faylor
2014-05-14  1:51                     ` Steven Penny
2014-05-14  3:01                       ` Christopher Faylor
2014-05-31 13:29                         ` PolarStorm
2014-05-29 17:45               ` David Conrad
2014-05-29 17:48                 ` Christopher Faylor
2014-05-29 23:41                   ` Steven Penny
2014-05-30  1:23                     ` Chris J. Breisch
2014-05-30  1:42                       ` Steven Penny
2014-05-30  9:05                         ` Christopher Faylor
2014-05-30 16:19                         ` Chris J. Breisch
2014-05-13 13:31         ` Christopher Faylor
2014-05-13 14:52         ` Chris J. Breisch
2014-05-13 19:17   ` Christian Franke

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=53726637.8040301@breisch.org \
    --to=chris.ml@breisch.org \
    --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).