On Wed, 2002-07-17 at 09:58, Michael D. Schleif wrote: > > Mike Noyes wrote: > > > > On Wed, 2002-07-17 at 08:58, Michael D. Schleif wrote: > > > Mike Noyes wrote: > > > > > > > > Anyone, > > > > Will removing the following lines from enforce_naming leave the perl > > > > script functional? > > > > > > Yes, absolutely yes; provided that either all of the lines are > > > completely _removed_ or completely commented out. > > > > Hmm, then what did I do wrong in rev 1.2? I used vi to dd out the lines > > below, and you ended up with a broken pipe from the server last night. > > > > Any enlightenment is appreciated. > > Previously, you said that _cvs import_ somehow bypasses case checking, > or this script. Since all I did last night was _cvs import_, and > because there is nothing in enforce_naming (no version in cvs) that > would result in "broken pipe" errors, I believe the culprit is > elsewhere.
Michael, It seems to, but I don't think it should. Our commitinfo seems to process our cvs_acls script but not enforce_naming on imports. I need to find a reference to what commands activate commitinfo in which circumstances. > > > Also, remove the lone `next;' at end of for loop, since the for loop > > > does that automatically, by design ;> > > > > Is this true for older versions of perl too? The SF cvs server may not > > have the newest perl release on it. > > I've been Perl'ing since v4.0x days. That is the design of a for loop. > That `next;' does not do anything bad except waste a couple cpu cycles . Thanks for the info. I'll remove it also. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
