From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin-talk@cygwin.com" <cygwin-talk@cygwin.com>
Subject: RE: New Cygwin release
Date: Sun, 27 May 2012 03:35:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A20A770AB41C@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <CAC4i1z2U2EG4Kwh-urwMWtU5FPKy1Lgh4XKHJNMLp+CkNcPPeg@mail.gmail.com>
David Eisner sent the following at Saturday, May 26, 2012 6:35 PM
>> 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.
>
>I'm reading between the lines, but are you of the opinion that the
>hostile tone is a helpful way to keep users from sending such messages
>in the future?
It's my fault. I mentioned that Chris seemed to have mellowed so one might
have expected that he might try to prove otherwise. But it still not to
the old standard. (Sorry, Chris.)
The advantage of WJM is that people who are paying attention and want to
avoid flames take care to be respectful, thankful, and avoid being
presumptuous. That is certainly what I've tried to do.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
prev parent reply other threads:[~2012-05-27 3:35 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
2012-05-26 22:35 ` David Eisner
2012-05-26 23:22 ` Linda Walsh
2012-05-27 3:35 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
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=0105D5C1E0353146B1B222348B0411A20A770AB41C@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--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).