public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: git stash damaged?
Date: Thu, 19 Jan 2017 17:24:00 -0000	[thread overview]
Message-ID: <6c283005-ec89-f2e3-a556-b018e8bbbb4e@SystematicSw.ab.ca> (raw)
In-Reply-To: <4f649dfd-bb02-3d41-9e74-69b7440a2ad3@anyces.com>

On 2017-01-19 07:47, Olivier FAURAX wrote:
> When I use "git stash", I get a message saying it is there but not
> executable.
> $ git stash
> fatal: 'stash' appears to be a git command, but we were not
> able to execute it. Maybe git-stash is broken?
> I tested with 2.8.3-1 and 2.8.2-1.
> I checked /usr/libexec/git-core/git-stash and it is a script that has
> proper permissions.
> Can you reproduce? (package: git)

$ file /usr/libexec/git-core/git-stash

and check if it mentions, DOS, BOM, or CRLF line terminators - fix with: 

$ dos2unix -k /usr/libexec/git-core/git-stash

then recheck permissions still executable.

If that's not it, post output of: 

$ ls -Adl .git
$ uname -srvmo
$ git --version
$ file    /usr/libexec/git-core/git-stash
$ ls -l   /usr/libexec/git-core/git-stash
$ getfacl /usr/libexec/git-core/git-stash
$ icacls  `cygpath -w /usr/libexec/git-core/git-stash`

to see if anything looks off.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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-19 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 14:48 Olivier FAURAX
2017-01-19 17:24 ` Brian Inglis [this message]
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

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=6c283005-ec89-f2e3-a556-b018e8bbbb4e@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).