All of lore.kernel.org
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Replace perl code with pure shell code
Date: Mon, 29 Jan 2007 04:54:37 -0800	[thread overview]
Message-ID: <86bqkidmcy.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <epkq3v$66p$1@sea.gmane.org> (Jakub Narebski's message of "Mon, 29 Jan 2007 13:43:54 +0100")

>>>>> "Jakub" == Jakub Narebski <jnareb@gmail.com> writes:

Jakub> Nevertheless Perl embedded in shell script is (a bit) horrible.

I will agree with that.  Either all Perl, or all shell, unless there's
an operation that begs for portability for which Perl can be an asset.

-- 
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:[~2007-01-29 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29  8:09 [PATCH] Replace perl code with pure shell code Simon 'corecode' Schubert
2007-01-29  8:56 ` Junio C Hamano
2007-01-29  9:18   ` Simon 'corecode' Schubert
2007-01-29  9:28     ` Shawn O. Pearce
2007-01-29 11:41 ` Randal L. Schwartz
2007-01-29 12:38   ` Nikolai Weibull
2007-01-29 12:53     ` Randal L. Schwartz
2007-01-29 13:17       ` Nikolai Weibull
2007-01-29 13:21         ` Randal L. Schwartz
2007-01-30 10:57       ` Junio C Hamano
2007-01-29 12:43   ` Jakub Narebski
2007-01-29 12:54     ` 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=86bqkidmcy.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.