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.
> From: Bo Berglund [mailto:Bo.Berglund at system3r.se] > Sent: Thursday, 19 January, 2006 12:23 > To: Michael Wojcik > Cc: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > > Something is missing here. Please read the CVSNT > documentation for the verifymsg script: > > <quote> > The template must include a program name, and can include > any number of arguments. If no other formatting is used %l is > automatically added which appends the full path to the current > log message file file to the template. > </quote> > > What verifymsg supplies is the path to a file which contains > the log message! > So your script must get the path from the command line > argument and then open that file and check its contents. > The log message is NOT sent to STDIN or some such. > > It is all in the CVSNT helpfile, please read it. No doubt that's helpful for the OP, but I'm not the one trying to use verifymsg, and my response was addressed specifically to the question of how to process stdin in a Windows cmd script. -- Michael Wojcik Principal Software Systems Developer, Micro Focus