From: merlyn@stonehenge.com (Randal L. Schwartz)
To: "Nikolai Weibull" <now@bitwi.se>
Cc: "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de>, git@vger.kernel.org
Subject: Re: [PATCH] Replace perl code with pure shell code
Date: Mon, 29 Jan 2007 04:53:17 -0800 [thread overview]
Message-ID: <86fy9udmf6.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <dbfc82860701290438y4e00cc05s5f8c8acdc8022768@mail.gmail.com> (Nikolai Weibull's message of "Mon, 29 Jan 2007 13:38:31 +0100")
>>>>> "Nikolai" == Nikolai Weibull <now@bitwi.se> writes:
Nikolai> We do require a POSIX-compliant version of sh already, right?
OK, sorry for raising the flag. I just know that writing portable shell
is far trickier than writing portable Perl, so I get overly cautious
on anything that wasn't in Unix V7.
--
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!
next prev parent reply other threads:[~2007-01-29 12:53 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 [this message]
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
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=86fy9udmf6.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=corecode@fs.ei.tum.de \
--cc=git@vger.kernel.org \
--cc=now@bitwi.se \
/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.