public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: merlyn@stonehenge•com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox•net>
Cc: Alex Riesen <raa.lkml@gmail•com>, git@vger•kernel.org
Subject: Re: [PATCH] git-mv.perl: use stderr for error output and cleanup
Date: 06 Jan 2006 14:55:54 -0800	[thread overview]
Message-ID: <86wthd7ypx.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7vek3lq8wu.fsf@assigned-by-dhcp.cox.net>

>>>>> "Junio" == Junio C Hamano <junkio@cox•net> writes:

Junio> So I'd prefer not touching for (@df) { print H "$_\n" } loops.

Being as I'm a *bit* familiar with Perl, I'd write that as:

  print H "$_\0" for @deletedfiles;

if you want to write "for" as "foreach", I wouldn't complain either.
After all, that's spelled "f o r", but pronounced "foreach". :)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge•com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2006-01-06 22:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 11:49 [PATCH] git-mv.perl: use stderr for error output and cleanup Alex Riesen
2006-01-06 22:38 ` Junio C Hamano
2006-01-06 22:55   ` Randal L. Schwartz [this message]
2006-01-06 23:28     ` Linus Torvalds
2006-01-06 23:53       ` Randal L. Schwartz
2006-01-07  0:10         ` Linus Torvalds
2006-01-07  0:46       ` Junio C Hamano
2006-01-07 10:28     ` Alex Riesen
2006-01-07 10:29       ` Junio C Hamano
2006-01-10 22:24         ` Alex Riesen
2006-01-07 10:34       ` Randal L. Schwartz
2006-01-07 21:04         ` Junio C Hamano
2006-01-08  0:07           ` Andreas Ericsson
2006-01-10 22:26         ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86wthd7ypx.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=junkio@cox$(echo .)net \
    --cc=raa.lkml@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox