[cvsnt] using commitinfo within CVSNT

Jeff Urlwin jurlwin at esoftmatic.com
Tue Nov 11 18:34:34 GMT 2003


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.


> 
> I'm not a PERL guy, so I can't help with your code.  
> Hopefully someone on the list can look and tell.

(from the perl perspective) Keep the while (<STDIN>) loop to read all of
STDIN. Is it possible the first line is blank?

Regards,

JEff
> 
> I do seem to recall once a problem someone had where PERL 
> invoked by association didn't get STDIN correctly, but 
> calling PERL.EXE with the script did work (or something like 
> that--search the archives here).
> 
> Regards,
> 
> Glen Starrett
>  
> 
> 
> > -----Original Message-----
> > 
> > Glen, it looks like I am still not picking it up right. Here
> > is the code
> > and output:
> > 
> > ***********PERL CODE****************
> > open MYLOG, ">>$LOGFILE";
> > print MYLOG "test.pl is being invoked\n";
> > my $file = <STDIN>;
> > print MYLOG "stdin is $file\n";
> > #while (<STDIN>) {
> > #  print MYLOG "current line is $_\n";
> > #}
> > close MYLOG;
> > 
> > *************OUTPUT********************
> > test.pl is being invoked
> > stdin is
> > 
> > Could you please help me with a code example?
> > 
> > Best Regards,
> > Suresh Venkateswaran
> > 
> > 
> > 
> > 
> >                                                               
> >                                                               
> >            
> >                       "Glen Starrett"                         
> >                                                               
> >            
> >                       <grstarrett at cox.n        To:       
> > Suresh Venkateswaran/San Jose/IBM at IBMUS, <cvsnt at cvsnt.org>    
> >                 
> >                       et>                      cc:            
> >                                                               
> >            
> >                                                Subject:  RE: 
> > [cvsnt] using commitinfo within CVSNT                         
> >             
> >                       11/10/2003 08:36                        
> >                                                               
> >            
> >                       PM                                      
> >                                                               
> >            
> >                                                               
> >                                                               
> >            
> >                                                               
> >                                                               
> >            
> > 
> > 
> > 
> > 
> > > However, when I print out the ARGV array from within my
> > Perl filtering
> > > script, it contains the base directory which is being 
> committed but 
> > > no file name information. I am able to access the file list in the
> > > loginfo file,
> > > which follows the commitinfo file in the logical sequence, so
> > > I should be
> > > able to access this information somewhere at the 
> commitinfo stage!!
> > 
> > Check stdin instead--it was changed to that to be 
> consistent and more 
> > scalable
> > 
> > From http://www.cvsnt.org/wiki/HistoryPage :
> > >>>
> > 14/07/03: 2.0.6: Change behaviour of commitinfo to use 
> stdin. Fix path 
> > detection on control panel. <<<
> > 
> > Glen Starrett
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook
> 




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