public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /bin/sh is not really bash? [was: git stash damaged?]
Date: Thu, 26 Jan 2017 15:13:00 -0000	[thread overview]
Message-ID: <f7a5190c-4959-6b6c-9efd-435339853329@gmail.com> (raw)
In-Reply-To: <699a278b-af6e-da03-f087-008b3d8317c0@gmail.com>

On 26/01/2017 15:20, cyg Simple wrote:
> On 1/26/2017 5:52 AM, Olivier FAURAX wrote:
>> Le 20/01/2017 à 16:20, Brian Inglis a écrit :

>>
>> Also, the previous link says that "/bin/sh is really bash", but:
>> $ /bin/sh --version
>>
>> $ /bin/bash --version
>> GNU bash, version 4.3.48(8)-release (x86_64-unknown-cygwin)
>>
>> Is this expected?
>>
>
> No.
>
> $ sh --version
> GNU bash, version 4.3.48(8)-release (x86_64-unknown-cygwin)
>
> You might want to check what your /bin/sh actually is or perhaps just
> remove it and set the symlink yourself.
>

e.g.

$ type sh
sh is hashed (/usr/bin/sh)

$ sh --version
GNU bash, version 4.4.11(2)-release (x86_64-unknown-cygwin)


--
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

  reply	other threads:[~2017-01-26 15:13 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 [this message]
2017-01-26 19:15         ` Hans-Bernhard Bröker

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=f7a5190c-4959-6b6c-9efd-435339853329@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).