Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Reply-To:	<nhv AT cape DOT com>
From:	"Norman Vine" <nhv AT cape DOT com>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	RE: cygwin slowdown in current cvs version -- need a volunteer
Date:	Sat, 8 Sep 2001 13:43:59 -0400
Message-ID:	<002c01c1388d$d7abf6c0$a300a8c0@nhv>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook 8.5, Build 4.71.2232.26
In-Reply-To:	<20010908133124.A12571@redhat.com>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
Importance:	Normal

Christopher Faylor writes:
>
>The keyword here, though, is "automatic".  If you have to remember
>to do it, then that sounds like a big imposition.  IMO, It'll also be
>more likely to be reliable if you remove the human element as much
>as possible.

If I could figure out how to logon to the CVS server from a python script
ie give the password when requested by the pserver I can probably
just make this a 'cron' thingy.

Everything else 
blowing away the old build dir, configure, make and now make check
is already driven by a script that times each part of the operation
and writes a little report for me.

FYI  I am also on a dial up ...

Cheers

Norman

- Raw text -