From: Johannes Sixt <j6t@kdbg•org>
To: Ben Walton <bdwalton@gmail•com>
Cc: gitster@pobox•com, git@vger•kernel.org, sunshine@sunshineco•com,
johannes.schindelin@gmx•de
Subject: Re: [PATCH 3/3] Fix sed usage in tests to work around broken xpg4/sed on Solaris
Date: Sun, 19 Jul 2015 22:22:51 +0200 [thread overview]
Message-ID: <55AC071B.9040800@kdbg.org> (raw)
In-Reply-To: <1437328836-19156-4-git-send-email-bdwalton@gmail.com>
Am 19.07.2015 um 20:00 schrieb Ben Walton:
> - sed -e s/CHANGE_ME/change_me/ <file >file+ &&
> + perl -pne "s/CHANGE_ME/change_me/" file >file+ &&
Did you mean '-lpe' or better '-pe' here?
-- Hannes
prev parent reply other threads:[~2015-07-19 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 18:00 Adapt some tests to work around broken Solaris tools Ben Walton
2015-07-19 18:00 ` [PATCH 1/3] Modify tr expressions so that xpg4/tr handles it on Solaris Ben Walton
2015-07-19 21:49 ` Eric Sunshine
2015-07-19 18:00 ` [PATCH 2/3] Fix sed usage in tests to work around broken xpg4/sed " Ben Walton
2015-07-19 18:00 ` [PATCH 3/3] " Ben Walton
2015-07-19 20:22 ` Johannes Sixt [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=55AC071B.9040800@kdbg.org \
--to=j6t@kdbg$(echo .)org \
--cc=bdwalton@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=johannes.schindelin@gmx$(echo .)de \
--cc=sunshine@sunshineco$(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