X-Spam-Check-By: sourceware.org
Message-ID: <10845a340604040128k14627ef8h869a937d943e94d0@mail.gmail.com>
Date: Tue, 4 Apr 2006 09:28:42 +0100
From: "Richard Quadling" <rquadling AT googlemail DOT com>
Reply-To: RQuadling AT googlemail DOT com
To: cygwin AT cygwin DOT com
Subject: Some pointers required on log file examination.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id k348SqHx024208

Hi.
I have a document building process which gets its data from a CVS andthen autoconf/configure/make...
The CVS command I'm using produces 2 log files. The first (cvs1.log)contains all the directory names. The second (cvs2.log) contains theactual changes to the local files.
What I want to do is not proceed with a nearly 3 hour make when theamount of changes is small.
By small I mean less than 50 files changed.
Also, if one from a specific set of files has changed then the makemust go ahead.
If the make is NOT to go ahead, then the current cvs2.log is to bekept and appended to the next time round, so eventually 50 files WILLhave changed and off we go.
I know next to nothing about Cygwin, so please be nice.
Where do I start?
Thank you,
Richard Quadling.
-------Fight back spam! Download the Blue Frog.http://www.bluesecurity.com/register/s?user=UlF1YWRsaW5n