[cvsnt] Re: How to debug loginfo handling?

Tony Hoyle tmh at nothing-on.tv
Thu Aug 15 20:28:40 BST 2002

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 Thu, 15 Aug 2002 19:11:03 GMT, bo.berglund at telia.com (Bo Berglund)

>Is there some way to debug what is happening on commits with CVSNT?
>Why should CVSNT refrain from triggering loginfo when there are two
>files in the commit but not when there is a single file???
>A CVSNT bug maybe?

We use loginfo here all the time (we have a loginfo script that
collates all the commits together, then sends an email when the last
directory has been sent)... It is probably working :-)

Use 'cvs -t' to see what the script handler is doing. Generally I
found things worked better when the full path was given in the

>All my commits are sent in with WinCvs, the successful commands are
>done by highlighting one file and clicking the red arrow.
>The unsuccessful commits are done by selecting the module dir in the
>left pane and activating the red arrow. Should not be a difference...

There shouldn't be a difference.

loginfo only gets called if there are really files to commit.  You can
sometimes get a 'modified' file in WinCVS that isn't really modified,
so a commit will ignore it.  


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook