From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114431 invoked by alias); 26 Jan 2017 19:15:33 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 114414 invoked by uid 89); 26 Jan 2017 19:15:31 -0000 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 Received: from mailout07.t-online.de (HELO mailout07.t-online.de) (194.25.134.83) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 26 Jan 2017 19:15:21 +0000 Received: from fwd34.aul.t-online.de (fwd34.aul.t-online.de [172.20.26.145]) by mailout07.t-online.de (Postfix) with SMTP id C2B6842CD66C for ; Thu, 26 Jan 2017 20:15:13 +0100 (CET) Received: from [192.168.2.28] (EkIFJ2ZrrhZsxyF9XOjqp-Uaz-702yAt7dd31-pDZ8h3aX884qGySlAcIMU5OAygG9@[91.59.16.4]) by fwd34.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1cWpVn-27Jg360; Thu, 26 Jan 2017 20:15:11 +0100 Subject: Re: /bin/sh is not really bash? [was: git stash damaged?] To: cygwin@cygwin.com References: <79a57b23-6050-e3d6-3cc9-776eade485af@SystematicSw.ab.ca> <1939fb92-8d67-4861-d7c8-5f5abca68496@anyces.com> From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= Message-ID: <1aa80c9d-4da5-a6f1-4295-580a32aae5b0@t-online.de> Date: Thu, 26 Jan 2017 19:15:00 -0000 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> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-01/txt/msg00319.txt.bz2 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