On Tue, Dec 15, 2009 at 08:53:56PM -0500, Brad Tilley wrote:
> If these are annoying, I will stop sending.
please submit this diff to upstream as it's maintained there, not in our
tree.

cheers,
jasper

> # cvs diff -Nup gnu/usr.bin/perl/util.c
> Index: gnu/usr.bin/perl/util.c
> ===================================================================
> RCS file: /cvs/src/gnu/usr.bin/perl/util.c,v
> retrieving revision 1.13
> diff -N -u -p gnu/usr.bin/perl/util.c
> --- gnu/usr.bin/perl/util.c     12 Oct 2009 18:24:22 -0000      1.13
> +++ gnu/usr.bin/perl/util.c     16 Dec 2009 01:51:34 -0000
> @@ -2507,7 +2507,7 @@ Perl_my_popen(pTHX_ const char *cmd, const char
> *mode)
> 
>  #ifdef PERLIO_USING_CRLF
>     /* Since we circumvent IO layers when we manipulate low-level
> -      filedescriptors directly, need to manually switch to the
> +      file descriptors directly, need to manually switch to the
>        default, binary, low-level mode; see PerlIOBuf_open(). */
>     PerlLIO_setmode((*mode == 'r'), O_BINARY);
>  #endif
> @@ -2971,7 +2971,7 @@ Perl_wait4pid(pTHX_ Pid_t pid, int *statusp, int
> flags
>                 *statusp = SvIVX(sv);
>                 /* The hash iterator is currently on this entry, so
>                 simply
>                    calling hv_delete would trigger the lazy delete,
>                    which on
> -                  aggregate does more work, beacuse next call to
> hv_iterinit()
> +                  aggregate does more work, because next call to
> hv_iterinit()
>                    would spot the flag, and have to call the delete
>                    routine,
>                    while in the meantime any new entries can't re-use
>                    that
>                    memory.  */
> @@ -4071,7 +4071,7 @@ Fill the sv with current working directory
>  /* Originally written in Perl by John Bazik; rewritten in C by Ben
>  Sugars.
>   * rewritten again by dougm, optimized for use with xs TARG, and to
>   prefer
>   * getcwd(3) if available
> - * Comments from the orignal:
> + * Comments from the original:
>   *     This is a faster version of getcwd.  It's also more dangerous
>   *     because you might chdir out of a directory that you can't chdir
>   *     back into. */
> 

-- 
"Intelligence should guide our actions, but in harmony with the
  texture of the situation at hand"
        -- Francisco Varela

Reply via email to