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
X-Authentication-Warning:	eos.vss.fsi.com: ford owned process doing -bs
Date:	Thu, 15 Jan 2004 12:41:33 -0600 (CST)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT eos
To:	cygwin AT cygwin DOT com
Subject:	RE: CVS b0rked?
In-Reply-To:	<NUTMEGPZJO3vg8lvJFs00000135@NUTMEG.CAM.ARTIMI.COM>
Message-ID:	<Pine.GSO.4.58.0401151229440.23399@eos>
References:	<NUTMEGPZJO3vg8lvJFs00000135 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
MIME-Version:	1.0
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

On Thu, 15 Jan 2004, Dave Korn wrote:
> Brian Ford wrote:
> > -----Original Message-----
> > From: Brian Ford [mailto:spamspamspam AT eggchipsandspam]
> > Sent: 15 January 2004 17:50
> > To: Dave Korn
> > Cc: cygwin[snip]
> > Subject: RE: CVS b0rked?
> >
I think we would all prefer that even the cygwin list address be trivially
concealed.

> > Please don't include plain text email addresses in the body
> > of messages.
> > They are food for spam harvesters.  I imagine this was just
> > an oversight as I think I have seen you remove them before?
> >
>   Oops, yes indeed.  Sorry.  It happened because I replied to the copy you
> sent me directly instead of to the copy which came via the listserv with the
> redacted headers.  So I quoted an addy, but then again you've been Cc'ing
> posters as well as sending to the list.  Chalk us up one minor breach of
> list etiquette each!
>
Have you seen this?

http://www.cygwin.com/ml/cygwin/2003-12/msg00641.html

I must admit that with that option available, I'm too lazy to check or
remember who is on the list and who is not.  I just take the default reply
my mailer (pine) presents to me.  I think that is as much as anyone can
reasonably ask.

> > You could try to debug it :).
>
>   Ya never know, I might just do that.  Is it worth rebuilding with
> --enable-debugging at configure time ?  I dunno how much worthwhile that
> will actually give me....
>
IIRC, --enable-debugging just adds more verbose logging (primarily
strace) and enables CYGWIN_DEBUG functionality.  So, it is probably not
worth it.  Just debug with the version you've got.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

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

- Raw text -