From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: New Cygwin release
Date: Sat, 26 May 2012 21:39:00 -0000 [thread overview]
Message-ID: <20120526213854.GA10950@ednor.casa.cgf.cx> (raw)
In-Reply-To: <CAC4i1z19TZmCzpN0Ese=5-vciYUGdRx-OYVFN9eW0SNyGDko2A@mail.gmail.com>
On Fri, May 25, 2012 at 05:05:16PM -0400, David Eisner wrote:
>INSIARPCDAWFFUIHITSWKMTPLAOTFATPTIODIACIASTWAMPWTGYPAYHIPNHDNANWTSTW
>(I'm not sure I agree. Reasonable people can disagree about whether
>feedback from users is helpful in these situations. Who knows, maybe
>the project leads are on the fence, and this pushes them in one
>direction. In any case, I am sure there was a more polite way to get
>your point across. Your hostility is probably not helpful --
>definitely not a nice way to start the weekend.)
Sorry but the "project leads" don't need joe users making obvious
suggestions. We've obviously made many previous releases and don't
require a vague suggestion from someone to realize when it is time
for a new one.
Earnie's observations were spot on. As a project maintainer himself he
knows what a waste of bandwidth these messages are. If his message will
make someone think twice before sending something a similar "why don't
you do your job" message then that's a good thing.
cgf
next prev parent reply other threads:[~2012-05-26 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <COL102-W17C80C7AC116C427EA7231B5010@phx.gbl>
[not found] ` <CA+sc5m=OWVvx+tJpxsbsW+BGe876wUj6AVB7kcNJqYyvViFJyQ@mail.gmail.com>
2012-05-25 21:05 ` David Eisner
2012-05-26 21:39 ` Christopher Faylor [this message]
2012-05-26 22:35 ` David Eisner
2012-05-26 23:22 ` Linda Walsh
2012-05-27 3:35 ` Buchbinder, Barry (NIH/NIAID) [E]
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=20120526213854.GA10950@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-talk@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).