From: Jeff King <peff@peff.net>
To: Marcel Koeppen <git-dev@marzelpan.de>
Cc: gitster@pobox.com, git@vger.kernel.org, sbejar@gmail.com
Subject: Re: [PATCH] Replace in-place sed in t7502-commit
Date: Fri, 16 May 2008 05:56:07 -0400 [thread overview]
Message-ID: <20080516095606.GA25045@sigill.intra.peff.net> (raw)
In-Reply-To: <1210897303-80828-1-git-send-email-git-dev@marzelpan.de>
On Fri, May 16, 2008 at 02:21:43AM +0200, Marcel Koeppen wrote:
> The in-place mode of sed used in t7502-commit is a non-POSIX extension.
> That call of sed is replaced by a more portable version using a
> temporary file.
Thanks, this fixes a similar issue on FreeBSD (which is probably the
same sed).
-Peff
prev parent reply other threads:[~2008-05-16 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 2:19 [PATCH] Fix sed syntax in t7502-commit for OSX Marcel Koeppen
2008-05-15 8:37 ` Junio C Hamano
2008-05-15 8:58 ` Holger Schurig
2008-05-15 11:06 ` Marcel Koeppen
2008-05-15 9:37 ` Santi Béjar
2008-05-16 0:21 ` [PATCH] Replace in-place sed in t7502-commit Marcel Koeppen
2008-05-16 9:56 ` Jeff King [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=20080516095606.GA25045@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git-dev@marzelpan.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbejar@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 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).