a question about loginfo commit emails

Folks, I'm planning to set up CVSROOT/loginfo to deliver commit emails. After reading 'info cvs', I found that cvs provides stuffs like %svV to access file name and revision information of a commit operation. I'd love to include the log message, i.e. what '-m' specifies in a 'cvs commit', in

Re: a question about loginfo commit emails

Isaac Claymore wrote: I'd love to include the log message, i.e. what '-m' specifies in a 'cvs commit', in commit mails, but cannot figure out how to retrieve that information. The commmit message is passed to the script via STDIN. -Matt ___

failed to read diff file header for binary files

hi all, typing: cvs rdiff -rTAG1 -rTAG2 project test.txt cvs server: failed to read diff file header /tmp/cvsR485Y3 for ExperimentInfo.frx,v: end of file using 1.11.1.2 on redhat server. it seems to be for files marked with -kb. should i be worried about this? the end of file bit has me a

Re: failed to read diff file header for binary files

Matthew Herrmann writes: cvs server: failed to read diff file header /tmp/cvsR485Y3 for ExperimentInfo.frx,v: end of file using 1.11.1.2 on redhat server. it seems to be for files marked with -kb. That's to be expected. Diff won't diff binary files by default -- instead of the normal

cvs history: warning: history line invalid

Hello. We've been getting these errors with cvs history: cvs history: warning: history line 51999 invalid cvs history: warning: history line 61598 invalid cvs history: warning: history line 61602 invalid Here is what's around line 51999 in the history file:

Repository troubles - expert help needed

I am having serious problems, and need help. I suspect that my repository is corrupted. I would like to know what to do to fix it. As part of the project documentation, I checked in the WinCVS user's guide. This is 1 html file, wincvs11.htm, and about 60 images named