From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t0005: ksh93 portability workaround
Date: Tue, 31 May 2016 16:17:01 -0700 [thread overview]
Message-ID: <xmqqwpm924ya.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160531230301.GB4585@sigill.intra.peff.net> (Jeff King's message of "Tue, 31 May 2016 19:03:01 -0400")
Jeff King <peff@peff.net> writes:
> Hmm. We discussed these back in:
>
> http://thread.gmane.org/gmane.comp.version-control.git/268657
>
> but I thought we decided not to do anything about them (according to
> that thread, I found a bunch of other ksh93 oddities, but maybe we've
> since fixed them?).
OK, I completely forgot about that topic.
Sorry for the noise. Let's drop it.
Thanks for reminding me of that thread; I would have been stumped
with the "cd ../.git/objects" thing and wasted a lot of time.
next prev parent reply other threads:[~2016-05-31 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 22:47 [PATCH] t0005: ksh93 portability workaround Junio C Hamano
2016-05-31 22:49 ` Eric Sunshine
2016-05-31 23:03 ` Jeff King
2016-05-31 23:17 ` Junio C Hamano [this message]
2016-05-31 23:04 ` [PATCH] t/lib-git-daemon: ksh " Junio C Hamano
2016-05-31 23:05 ` Jeff King
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=xmqqwpm924ya.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).