/bin/sh is not really bash? [was: git stash damaged?]

Hans-Bernhard Bröker HBBroeker@t-online.de
Thu Jan 26 19:15:00 GMT 2017

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

More information about the Cygwin mailing list