From: Jeff King <peff@peff.net>
To: Armin Kunaschik <megabreit@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: Portability of git shell scripts?
Date: Fri, 6 May 2016 22:53:20 -0400 [thread overview]
Message-ID: <20160507025320.GA31460@sigill.intra.peff.net> (raw)
In-Reply-To: <CALR6jEiWQUO0WsOVah2O+9-j2Qx7juYjP7cb1v+P=Ey0oqQszg@mail.gmail.com>
On Fri, May 06, 2016 at 06:57:45PM +0200, Armin Kunaschik wrote:
> > Right. Any modern-ish Bourne shell will do, so moving to bash is one
> > way to fix it.
>
> My last compile of git 2.2.2 did far better than the current 2.8.2. So
> it looks like there were more recent changes that broke portability.
If you have a working version and a non-working version, the results of
"git bisect" would be very helpful to find the change (or the output of
the test run with "-v -i" to show what's going on in the failing test).
-Peff
prev parent reply other threads:[~2016-05-07 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 18:17 Portability of git shell scripts? Armin Kunaschik
2016-05-04 18:35 ` Torsten Bögershausen
2016-05-04 21:20 ` Jeff King
2016-05-06 16:57 ` Armin Kunaschik
2016-05-07 2:53 ` 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=20160507025320.GA31460@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=megabreit@googlemail.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).