X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=hff6GyxLN4QCfjZu
	Yc4FPtdiKU48edGt8L8CDumEHX82wcu5V51DFPH++cX9kxnx8Dg3FZCpPh2HDVWp
	+8Q3g+uqaGg+/Bf4qm8zz96rv4Ed2tz7dcS2ojLWQrwf1EhejGMjWEPZaSApwwWn
	Q55fJDadcIY1JXsBpse1m8DWgwQ=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=km4z25eDo21zzGGQldNEgd
	6yjh4=; b=pvSyJg0DOJ940onrcbA0jcPDdLs66M5GWhS2zhnVa9umejigVKaIeF
	hono1P4P4jdCUtwTJ7mdEslQXcwh6n8m1FJwn0jz/7/SBDOOiH9bNFs0QLOIgGHu
	Bkk8yyYJEeueLihd3A5Z4NsCZ955mRU0Io6BNaHks2BWj+G0K0H4A=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-3.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=26012017, H*Ad:D*t-online.de, activity
X-HELO:	mailout07.t-online.de
Subject:	Re: /bin/sh is not really bash? [was: git stash damaged?]
To:	cygwin AT cygwin DOT com
References:	<79a57b23-6050-e3d6-3cc9-776eade485af AT SystematicSw DOT ab DOT ca> <1939fb92-8d67-4861-d7c8-5f5abca68496 AT anyces DOT com>
From:	=?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID:	<1aa80c9d-4da5-a6f1-4295-580a32aae5b0@t-online.de>
Date:	Thu, 26 Jan 2017 20:15:06 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version:	1.0
In-Reply-To:	<1939fb92-8d67-4861-d7c8-5f5abca68496@anyces.com>
X-IsSubscribed:	yes

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

- Raw text -