From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: /bin/sh is not really bash? [was: git stash damaged?]
Date: Thu, 26 Jan 2017 19:15:00 -0000 [thread overview]
Message-ID: <1aa80c9d-4da5-a6f1-4295-580a32aae5b0@t-online.de> (raw)
In-Reply-To: <1939fb92-8d67-4861-d7c8-5f5abca68496@anyces.com>
Am 26.01.2017 um 11:52 schrieb Olivier FAURAX:
> I found a workaround by replacing:
> #!/bin/sh
> by:
> #!/bin/bash
> in the first line of /usr/libexec/git-core/git-submodule
If that change has any effect, that leaves three main possibilities:
1) something broke or otherwise disabled your installed /bin/sh.exe, but
left /bin/bash.exe intact. Someone else here had some unrelated
activity kill cygwin's bash.exe recently...
2) the git-stash script wrongly assumes bash behaves exactly the same
when called as 'sh' and as 'bash'. But bash enters POSIX compatibility
mode in that case, which disables quite a number of GNU extensions.
> This might be related to:
> https://cygwin.com/faq/faq.html#faq.using.shell-scripts
That would be case 2) I don't think so, though. The symptoms of that
would be less blunt than "could not execute".
> Also, the previous link says that "/bin/sh is really bash", but:
> $ /bin/sh --version
That strongly hints you have case 1) happening here.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2017-01-26 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 14:48 git stash damaged? Olivier FAURAX
2017-01-19 17:24 ` Brian Inglis
2017-01-20 13:00 ` Olivier FAURAX
2017-01-20 15:20 ` Brian Inglis
2017-01-26 10:52 ` /bin/sh is not really bash? [was: git stash damaged?] Olivier FAURAX
2017-01-26 14:21 ` cyg Simple
2017-01-26 15:13 ` Marco Atzeri
2017-01-26 19:15 ` Hans-Bernhard Bröker [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=1aa80c9d-4da5-a6f1-4295-580a32aae5b0@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).