Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 14 Oct 2003 10:40:42 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: merging mingw and cygwin
Message-ID: <20031014144042.GB16944@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20031013190000 DOT GB20245 AT mdssirds DOT comp DOT pge DOT com> <bmf0hl$fvb$1 AT sea DOT gmane DOT org> <20031013203527 DOT GA25036 AT mdssirds DOT comp DOT pge DOT com> <bmf39l$ls2$1 AT sea DOT gmane DOT org> <20031013213226 DOT GC25036 AT mdssirds DOT comp DOT pge DOT com> <bmf8as$kg7$1 AT sea DOT gmane DOT org> <20031013224522 DOT GB26012 AT mdssirds DOT comp DOT pge DOT com> <20031014021908 DOT GH22296 AT redhat DOT com> <20031014045910 DOT GB28478 AT mdssirds DOT comp DOT pge DOT com> <Pine DOT GSO DOT 4 DOT 56 DOT 0310140859080 DOT 20462 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.56.0310140859080.20462@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i

On Tue, Oct 14, 2003 at 09:08:56AM -0400, Igor Pechtchanski wrote:
>On Mon, 13 Oct 2003, Edward Peschko wrote:
>> On Mon, Oct 13, 2003 at 10:19:08PM -0400, Christopher Faylor wrote:
>>>[snip]
>>>Do not send me personal email about cygwin again.
>> [snip]
>>You hold the keys to some sort of power, the power to enter the
>>developer's list, the power to patch cygwin effectively.  For you to
>>issue a blanket statement that I am not to communicate to you about
>>cygwin and hence never to enter that list is a disabuse of power.
>>[snip]
>
>You don't get on the list by sending personal e-mail to the list
>maintainer -- you annoy the $#!% out of them that way.  There are
>mechanisms for subscribing to various lists, all of which are outlined
>on <http://cygwin.com/lists.html>.  Nowhere does it say that personal
>e-mail is one of them.

In Edward's defense (and just to demonstrate what a great guy I am), he
did follow the directions.  The problem was that he wanted to argue with
me when I mentioned that I didn't consider his plans to be
cygwin-developers worthy.  It was pretty obvious that his knowledge base
on cygwin and mingw was missing important bits and would benefit from
some distributed disabusement on the cygwin mailing list.  So I
(politely) referred him to that list, where he'd already started a
discussion.

Then he wanted to continue to argue, so I told him not to send me
personal email.

Then he sent me personal email again.  And you all saw the result.

So, say what you want but Edward followed the correct first step.  He
was just not successful in his attempt to join.  That happens from time
to time.

I don't know why he managed to follow the directions correctly for
cygwin-developers but still was dumbfounded to find that the cygwin
project is different from the perl5-porters project and used a
cygwin-patches list.  I had foolishly assumed that he already knew about
cygwin-patches when he sent the initial "please subscribe me" email to
cygwin-developers-owner.  And, it sure seemed like he was a long long
way away from ever submitting a patch.

Lapo does have the sense of this right.  I have no inclination to
personally engage people with their pet cygwin projects; especially
people who still have a lot of learning to do.  We set up the mailing
list so that we can all share the load of bringing "newbies" up to
speed.  I didn't sign on to be a personal tutor or, worse, a debater.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/