public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Churchill, Dan  \(MN65\)" <churchill_dan@htc.honeywell.com>,
	<cygwin@cygwin.com>
Subject: Re: WTF?!
Date: Fri, 21 Sep 2001 02:28:00 -0000	[thread overview]
Message-ID: <027401c1427f$f76696e0$0200a8c0@lifelesswks> (raw)
In-Reply-To: <D59EA43E31578445B543D05854E2957353B28F@mn65-exuser1.htc.honeywell.com>

----- Original Message -----
From: "Churchill, Dan (MN65)" <churchill_dan@htc.honeywell.com>
To: <cygwin@cygwin.com>
Sent: Friday, September 21, 2001 2:23 AM
Subject: RE: WTF?!


> Chris, you are obviously a _very_ intelligent programmer/person in
general
> (I have been reading the list for several weeks now).  No one would
complain
> if you restricted yourself to only answering questions that require
your
> knowledge, either as a developer of Cygwin or as a list maintainer.
This is
> a public list with lots of other readers who are not anywhere near
your
> level of knowledge of this project, but who are intelligent enough to
field
> questions that have obvious (to you, but not to everybody) answers.

Yup, and "we" (old timers) know this. In fact on the devel list we have
had discussions about how to address this. Chris at one point
deliberately did not email unless questions seemed missed. And we all
stuck up hands to answer various questions. Earnie covers "look here"
ones. I cover pthreads and thread questions. And so on.

It is *hard* when you care about a product to let those asking for help
go unanswered. One thing worth noting is that Chris *did not* field the
question, until three!!! (or was it two?!) incorrect responses followed
up the first one. So Chris was stepping in and saying "you've got this
wrong". And thats an important thing to do, otherwise those answers
spread misinformation...

That aside though, I agree with most of what you said.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-09-21  2:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20  9:23 WTF?! Churchill, Dan  (MN65)
2001-09-21  2:28 ` Robert Collins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-18  8:46 Binutils and GCC Christopher Faylor
2001-09-19 22:37 ` Binutils and GCC [LONG and mildly OT] Christopher Currie
2001-09-20  8:24   ` Christopher Faylor
2001-09-20  8:40     ` WTF?! Pavel Tsekov
2001-09-20  9:06       ` WTF?! Christopher Faylor
2001-09-20  9:28         ` WTF?! Pavel Tsekov
2001-09-20  9:39           ` WTF?! Larry Hall (RFK Partners, Inc)
2001-09-20  9:50             ` WTF?! Pavel Tsekov
2001-09-20  9:58               ` WTF?! Larry Hall (RFK Partners, Inc)
2001-09-20 10:30                 ` WTF?! Robert Praetorius
2001-09-20 10:47                   ` WTF?! Christopher Faylor
2001-09-20 11:17                     ` WTF?! Larry Hall (RFK Partners, Inc)
2001-09-20  9:50           ` WTF?! Christopher Faylor
     [not found] <003c01c0adf4$f7777340$db011fac@fer.ucs.co.za>
2001-03-16  1:18 ` WTF? Robert Collins
2001-03-16  5:54   ` WTF? Earnie Boyd
2001-03-16  7:32     ` WTF? Christopher Faylor
2001-03-16  0:32 WTF? Frans Rossouw
2001-03-16  0:36 ` WTF? Robert Collins
1998-01-17 13:14 WTF?! Andrew Dolphin

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='027401c1427f$f76696e0$0200a8c0@lifelesswks' \
    --to=robert.collins@itdomain.com.au \
    --cc=churchill_dan@htc.honeywell.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).