On 17 Jul 2002 10:24:21 PDT Mike Noyes wrote:

> Brad,
> Thanks for the proof. The broken pipe may have been a coincidence, but I
> thought I should check before trying this again.

Almost always better to be safe than sorry, I suppose. :)
 
> My diff doesn't look right (diff output below). The same thing happened
> last night when going from rev 1.1 to 1.2. Strange, the diff seems to be
> offset. Am I doing something wrong? I'll try the change in Emacs and see
> if the diff changes.
> 
> [Leaf-cvs-commits] CVSROOT enforce_naming,1.1,1.2
> http://www.mail-archive.com/leaf-cvs-commits%40lists.sourceforge.net/msg00039
>.html
> 
> 
> CVSROOT]$ diff enforce_naming ~/CVSROOT/enforce_naming 
> 26c26
> < # $Id: enforce_naming,v 1.3 2002/07/17 02:44:55 mhnoyes Exp $
> ---
> > # $Id: enforce_naming,v 1.4 2002/05/04 16:12:18 moorman Exp $
> 32a33
> > # 3. Verify that all filenames, except Makefile, are lowercase
> 46a48,54
> >               $exit_val = 1;
> >       }
> > 
> >       # Verify that all files are lowercase, except Makefiles
> >       if ((substr($_, 0, 8) ne "Makefile") and (lc($_) ne $_)) {
> >               print "All filenames must be completely lowercase except";
> >               print "Makefiles. ($directory/$_)\n";
> 

Looks okay to me.  The next line after the last "print" line
inserted is another "$exit_val = 1" line.  Even though your
diff looks different than mine, the resulting code is the same.

I also double-checked the r1.1 to r1.2 diff[1] from last night,
and I don't see anything wrong or any changes that should have
resulted in the broken pipe error.

What was the context of the broken pipe message?

--Brad

[1] 
http://cvs.leaf-project.org/cgi-bin/viewcvs.cgi/leaf/CVSROOT/enforce_naming.diff?r1=1.1&r2=1.2


-------------------------------------------------------
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

Reply via email to