public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: merlyn@stonehenge•com (Randal L. Schwartz)
To: Sverre Rabbelier <srabbelier@gmail•com>
Cc: Jakub Narebski <jnareb@gmail•com>,
	Jari Aalto <jari.aalto@cante•net>,
	git@vger•kernel.org
Subject: Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.
Date: Sat, 17 Apr 2010 15:58:43 -0700	[thread overview]
Message-ID: <86zl118z4s.fsf@red.stonehenge.com> (raw)
In-Reply-To: <g2xfabb9a1e1004171547we6a74176v4a697ded96e9f115@mail.gmail.com> (Sverre Rabbelier's message of "Sun, 18 Apr 2010 00:47:34 +0200")

>>>>> "Sverre" == Sverre Rabbelier <srabbelier@gmail•com> writes:

>> We use idiomatic Perl, e.g.

Sverre> Ah, I thought that the discussion was about whether the "$_" syntax
Sverre> was idiomatic or not. It got the impression that the "$ARG etc. is a
Sverre> failed experiment" was Randal's personal opinion, but if that's how
Sverre> the perl community has decided that things should be done than that's
Sverre> of course how we should do it :).

Yes.  Within the Perl community, $_ is idiomatic.

"use English" is discouraged.  It was an interesting experiment, but it
failed.

Please stop making me repeat myself.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge•com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

      reply	other threads:[~2010-04-17 22:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 16:09 [PATCH RFC 0/5] Patches to avoid reporting conversion changes Henrik Grubbström (Grubba)
2010-04-16 16:09 ` [PATCH RFC 1/5] sha1_file: Added index_blob() Henrik Grubbström (Grubba)
2010-04-16 16:09 ` [PATCH RFC 2/5] cache: Added ce_norm_sha1() and related cache_entry fields Henrik Grubbström (Grubba)
2010-04-16 16:10 ` [PATCH RFC 3/5] cache: Added index extension "NORM" Henrik Grubbström (Grubba)
2010-04-16 16:10 ` [PATCH RFC 4/5] reachable: Made the gc aware of the ce_norm_sha1 Henrik Grubbström (Grubba)
2010-04-16 16:10 ` [PATCH RFC 5/5] cache: Use ce_norm_sha1() Henrik Grubbström (Grubba)
2010-04-20  7:25   ` Junio C Hamano
2010-04-20 15:39     ` Henrik Grubbström
2010-04-20 19:12       ` Junio C Hamano
2010-04-25 11:25         ` Henrik Grubbström
2010-04-16 18:02 ` [PATCH RFC 0/5] Patches to avoid reporting conversion changes Jari Aalto
2010-04-16 18:06   ` Randal L. Schwartz
2010-04-17 19:32     ` Jari Aalto
2010-04-17 19:34       ` Randal L. Schwartz
2010-04-17 22:07         ` Sverre Rabbelier
2010-04-17 22:32           ` Jakub Narebski
2010-04-17 22:47             ` Sverre Rabbelier
2010-04-17 22:58               ` Randal L. Schwartz [this message]

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=86zl118z4s.fsf@red.stonehenge.com \
    --to=merlyn@stonehenge$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jari.aalto@cante$(echo .)net \
    --cc=jnareb@gmail$(echo .)com \
    --cc=srabbelier@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