public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "'cygwin-talk@cygwin.com'" <cygwin-talk@cygwin.com>
Subject: RE: snapshots revisited
Date: Sat, 12 Mar 2011 04:27:00 -0000	[thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A209DAA1007F@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <AANLkTinC6ba03h4dk7M=wZD-ZF=kXFBwqOj9NuV-0CC6@mail.gmail.com>

David Eisner sent the following at Friday, March 11, 2011 11:13 AM
>Here's my theory.  Chris was making a snarky comment

I don't know about anyone else, but I'll share how Chris's "style"
affects me.

I don't want to be the target of his (or anyone else's) ire.
Therefore, before hitting send, I carefully and critically review
my email to make sure that it is polite, respectful, unpresumptuous,
and thankful.  That is something that everyone should do anyway, but
Chris adds an incentive.

Think about it.  Every request is wrapped around a complaint.
"Please pass the water."  ("Why are you keeping the water over
there where I can't @#$%^ get it!")  So when people make an
effort to avoid triggering a reaction from Chris, the overall
tone of the list improves.  And when they don't, they shouldn't
complain about something that could have easily been avoided.

(However, I admit that appreciation of Chris's style is an acquired
taste.)

>Corrina is polite to list members in general, which is
>appreciated.)

Look at it this way.  Averaging Corinna's constant politeness with
Chris's curmudgeonliness yields a pleasant ambiance.

And if reading some snarky retorts is the price one pays for getting
free help with a great product (also free), we still are getting a
bargain.  If one wants support provided by Corinna and not Chris, I
suspect that arrangements can be made with Red Hat.  :-)

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

  parent reply	other threads:[~2011-03-12  4:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110310080923.19244yp07upxphcz@messagerie.si.c-s.fr>
     [not found] ` <20110310091353.GU12899@calimero.vinschen.de>
     [not found]   ` <20110310232423.GA3588@ednor.casa.cgf.cx>
     [not found]     ` <20110310232514.GA10198@ednor.casa.cgf.cx>
     [not found]       ` <20110311082012.GE7064@calimero.vinschen.de>
     [not found]         ` <20110311152511.GB4645@ednor.casa.cgf.cx>
     [not found]           ` <COL102-W10B426004D410A3549CE47B5CB0@phx.gbl>
2011-03-11 15:58             ` Christopher Faylor
2011-03-11 16:13             ` David Eisner
2011-03-11 16:18               ` Andy Koppe
2011-03-11 16:44                 ` Christopher Faylor
2011-03-12  4:27               ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2011-03-12 17:16                 ` Lee D. Rothstein
2011-03-12 17:41               ` Corinna Vinschen
2011-03-12 18:21                 ` Christopher Faylor
2011-03-12 18:39                   ` Corinna Vinschen
2011-03-12 18:55                     ` Christopher Faylor
2011-03-12 19:53                       ` Corinna Vinschen
2011-03-12 19:54                 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-03-12 20:10                   ` Corinna Vinschen
2011-03-12 21:11                     ` Christopher Faylor
2011-03-12 21:32                       ` Corinna Vinschen

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=0105D5C1E0353146B1B222348B0411A209DAA1007F@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).