From: "Miles Bader" <miles@gnu.org>
To: "David Kastrup" <dak@gnu.org>
Cc: "Wincent Colaiuta" <win@wincent.com>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Christian Couder" <chriscool@tuxfamily.org>,
"Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>
Subject: Re: [PATCH 1/3] git-bisect: war on "sed"
Date: Thu, 15 Nov 2007 20:00:14 +0900 [thread overview]
Message-ID: <fc339e4a0711150300n64b9d670o1e183553a9de0cba@mail.gmail.com> (raw)
In-Reply-To: <86tznn4y7v.fsf@lola.quinscape.zz>
On Nov 15, 2007 7:09 PM, David Kastrup <dak@gnu.org> wrote:
> > Er, I suppose -- if you are acquainted with that particular shell
> > variable syntax (I suspect knowledge of sed is far more widespread).
>
> sed is rather bad with regard to portability. If you take a look at
> the respective portability section in the autoconf file, it is almost
> longer than that of Bourne shells.
I don't think that's really a fair characterization -- almost all of
the autoconf sed portability caveats concern weird corner cases in the
dusty corners of the language (and some are "common" issues with other
tools, i.e., avoiding ^ and $ inside of regexp groups).
For typical straightforward usage, there seems little problem.
[The main portability problems I've actually _noticed_ with sed are
the "-e" versus ";" issue and what happens with "\n" in various
contexts...]
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2007-11-15 11:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 7:18 [PATCH v2] Bisect reset: remove bisect refs that may have been packed Christian Couder
2007-11-15 8:18 ` Junio C Hamano
2007-11-15 8:27 ` Johannes Sixt
2007-11-15 8:49 ` Shawn O. Pearce
2007-11-15 8:52 ` Jeff King
2007-11-15 12:10 ` Johannes Schindelin
2007-11-15 8:34 ` Junio C Hamano
2007-11-15 9:00 ` [PATCH 1/3] git-bisect: war on "sed" Junio C Hamano
2007-11-15 9:29 ` Miles Bader
2007-11-15 9:36 ` Wincent Colaiuta
2007-11-15 9:53 ` Miles Bader
2007-11-15 10:06 ` Andreas Ericsson
2007-11-15 10:14 ` David Kastrup
[not found] ` <86tznn4y7v.fsf@lola.quinscape.zz>
2007-11-15 11:00 ` Miles Bader [this message]
2007-11-15 11:18 ` David Kastrup
2007-11-15 12:59 ` Miles Bader
2007-11-15 9:01 ` [PATCH 2/3] git-bisect: use update-ref to mark good/bad commits Junio C Hamano
2007-11-15 9:01 ` [PATCH 3/3] git-bisect: modernize branch shuffling hack Junio C Hamano
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=fc339e4a0711150300n64b9d670o1e183553a9de0cba@mail.gmail.com \
--to=miles@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=win@wincent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).