From: Ben Walton <bwalton@artsci.utoronto.ca>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH 0/1] Re-roll of the test fix for sed on solaris
Date: Mon, 9 Jan 2012 21:47:32 -0500 [thread overview]
Message-ID: <1326163653-26565-1-git-send-email-bwalton@artsci.utoronto.ca> (raw)
In-Reply-To: <7vd3b0vc6h.fsf@alter.siamese.dyndns.org>
Hi Junio,
It seems that you were correct in that it's the exit status from sed
that ultimately causes the breakage. I've updated the commit message
to reflect this.
Thanks
-Ben
next prev parent reply other threads:[~2012-01-10 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 13:44 [PATCH] Work around sed portability issue in t8006-blame-textconv Ben Walton
2012-01-03 19:05 ` Junio C Hamano
2012-01-06 22:53 ` Junio C Hamano
2012-01-09 3:40 ` Ben Walton
2012-01-10 2:47 ` Ben Walton [this message]
2012-01-10 2:47 ` [PATCH] Use perl instead of sed for t8006-blame-textconv test Ben Walton
2012-01-10 4:46 ` [PATCH 0/1] Re-roll of the test fix for sed on solaris 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=1326163653-26565-1-git-send-email-bwalton@artsci.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).