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
Message-ID:	<03a101c0ff5e$5273bfa0$806410ac@local>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Jason Dufair" <jase AT dufair DOT org>, <cygwin AT cygwin DOT com>
References:	<00cb01c0ff50$e309a2e0$a300a8c0 AT nhv> <3B3A6563 DOT 3050504 AT dufair DOT org>
Subject:	Re: building cygwin with python script
Date:	Thu, 28 Jun 2001 09:10:13 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
X-OriginalArrivalTime:	27 Jun 2001 23:00:35.0869 (UTC) FILETIME=[F9C204D0:01C0FF5C]

----- Original Message -----
From: "Jason Dufair" <jase AT dufair DOT org>


> do the changes.  I'd need CVS access since I assume anoncvs can't commit
> changes.  Maybe we can put the Python script on the sources.redhat.com
> site somewhere?

The standard process is for a patch to be sent to cygwin-patches AT cygwin DOT com,
and then Chris commits the code after review. Few of the net maintainers
commit code directly to CVS.

> On a side note, should my new cygwin1.dll be ~5MB instead of ~645KB?  Is
> this just a side effect of the current snapshot?

It's a debug version. strip the .dll and you'll have a ~645Kb file.

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/

- Raw text -