Re: Some pointers required on log file examination.

On Tue, 4 Apr 2006, Igor Peshansky wrote: > Earlier, I wrote (regarding firing off the build once some number of files > have changed): > > > FWIW, a slightly better way of structuring your make is to remember the > > date/time of the last make (as a timestamp on a file, perhaps), and > > simply c

Re: Some pointers required on log file examination.

Earlier, I wrote (regarding firing off the build once some number of files have changed): > FWIW, a slightly better way of structuring your make is to remember the > date/time of the last make (as a timestamp on a file, perhaps), and > simply compare CVS as of that date/time with the HEAD. If the

Re: Some pointers required on log file examination.

Thanks for that. I'd not thought of using the CVS itself. Living and learning.

Re: Some pointers required on log file examination.

On Tue, 4 Apr 2006, Richard Quadling wrote: > Hi. > > I have a document building process which gets its data from a CVS and > then 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

Some pointers required on log file examination.

Hi. I have a document building process which gets its data from a CVS and then 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 the actual changes to the local files. What I want to do