Larry Lords wrote: > We are currently running cvs 1.11.6 on a Red Hat 8.0 server > with Windows XP > clients. I would appreciate help in resolving the following > questions: > > 1. I need to know and report the status (added, changed, or > removed) on each > committed file to a certain area of the repository. The > information I need to > report is: status, username, path within designated area, and > comment for the > committed file. I believe I can get all the information I > need except for the > status of the committed file. http://www.cvshome.org/docs/manual/cvs-1.11.15/cvs_18.html#SEC167 says that new files will not have an archive file (Unless they're being resurrected), and deleted files will not have a copy of the file in the current directory.
Now, how you're supposed to determine the file is not there is a bit challenging - I guess your script will have to parse the CVS/Entries file, and match up local files with entries in the CVS/Entries file. > 2. My understanding is if you commit files from multiple directories, > commitinfo will be called separately for each directory and > if the last time > commitinfo is called a non-zero is returned the entire commit > is aborted and > none of the files are committed. My question is how can I tell when a > supposedly good commit was aborted by a later file being > committed during the > same commit? I could be wrong, but I think you may be trying to stretch the capabilities of commitinfo here. Remember, it was designed simply as a pre-commit check, to see if it is acceptable to allow the checkin to proceed. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
