Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Mon, 15 Oct 2001 14:22:10 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Hit a problem with GDB and cygwin
Message-ID:	<20011015142210.B6984@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3BCAA443 DOT 23844 DOT 4B5ED0B4 AT localhost> <3BCB36E9 DOT 12942 DOT 11DE6C0 AT localhost>
Mime-Version:	1.0
In-Reply-To:	<3BCB36E9.12942.11DE6C0@localhost>
User-Agent:	Mutt/1.3.21i

On Mon, Oct 15, 2001 at 07:20:09PM +0200, Gerrit P. Haase wrote:
>>Your technique works great as long as you are always here to answer
>>questions.  It breaks down when you are not available.  On the other
>>hand, the mailing list archives are always going to be available so if
>>people get into the habit of checking them first they would be able to
>>answer their questions more quickly, and probably more definitively.
>
>I agree with this completely.

Then why don't you practice it?

cgf

--
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/

- Raw text -