From: Todd Zullinger <tmz@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH v2] t: allow use of "sed -E"
Date: Sat, 14 Mar 2026 19:16:42 -0400 [thread overview]
Message-ID: <abXsWp5gYbxdHbkz@teonanacatl.net> (raw)
In-Reply-To: <abKG1U3fVuNV1w_9@fruit.crustytoothpaste.net>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
brian m. carlson wrote:
> so this appears to be reasonably well supported across major open source
> distributions. The irony is that Linux is most likely the OS holding us
> back here, since older versions labeled this `-r` and the newer `-E`
> wasn't available in Ubuntu 16.04. I myself only recently learned about
> the fact that `-E` had been officially standardized, since I'd been
> using `-r` for a long time.
IIRC, GNU sed supported -E for a very long time before it
was documented. In a quick search, I see it added in v4.1a,
in commit 3a8e165 (treat cygwin CR/LF correctly (and by
design, not by chance), 2006-08-07).
https://cgit.git.savannah.gnu.org/cgit/sed.git/diff/sed/sed.c?id=3a8e165
--
Todd
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-03-14 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 21:35 [RFC] t: allow use of "sed -E" Junio C Hamano
2026-03-11 21:41 ` Junio C Hamano
2026-03-11 23:12 ` Ramsay Jones
2026-03-12 0:33 ` Junio C Hamano
2026-03-12 0:45 ` [PATCH v2] " Junio C Hamano
2026-03-12 6:41 ` Patrick Steinhardt
2026-03-12 9:26 ` brian m. carlson
2026-03-12 13:43 ` Junio C Hamano
2026-03-14 23:16 ` Todd Zullinger [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=abXsWp5gYbxdHbkz@teonanacatl.net \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.com \
--cc=szeder.dev@gmail.com \
--cc=tboegi@web.de \
/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