Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Wed, 11 Aug 2004 11:59:00 +0100, John Kinson <cvs at yellowradio.com> wrote: > >- The CVS/Entries file in the temporary sandbox can be used to obtain >information about the files being committed. Each line in the file has >5 fields with the following format: > > /<filename>/<old rev>/<old timestamp>/?/T<sticky tag> > ><old timestamp> is in GMT (UTC?). Not sure what's in the fourth field, >it's always been empty in my experiments. <old rev> is 0 for new files, >negative for removed files (with the absolute value equal to the >revision removed), and positive for modified files. http://www.cvsnt.org/manual/Working-directory-storage.html For a client-side script the repository information is always local. >- The new revision number for a file, if needed in a trigger script, can >be predicted by looking up the branch tag in the repository ,v file as >necessary (won't go into it here, but it seems straightforward enough). It's probably not a good idea to predict revision numbers (the user may have specified -r). It's not useful information prior to a commit actually happening though. >I've not considered what happens when files are renamed though, so this >information may need to be revised accordingly. That information is in the 'Renames' file, but I've not put that in the documentation yet. Tony