git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <sopq0asmppc9@online.de>
To: "'brian m. carlson'" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>
Subject: AW: Git commands throw error
Date: Mon, 22 Jun 2020 18:17:29 +0200	[thread overview]
Message-ID: <035a01d648b0$a24170d0$e6c45270$@online.de> (raw)
In-Reply-To: <20200618175232.GI6531@camp.crustytoothpaste.net>

Hi Brian,

thanks for your advice. I opened an issue on GitHub. Let's see where it takes me.

Regards, Thorsten

-----Ursprüngliche Nachricht-----
Von: brian m. carlson <sandals@crustytoothpaste.net> 
Gesendet: Donnerstag, 18. Juni 2020 19:53
An: sopq0asmppc9@online.de
Cc: git@vger.kernel.org
Betreff: Re: Git commands throw error

On 2020-06-18 at 04:58:27, sopq0asmppc9@online.de wrote:
> Hi!
> 
> I recently upgraded my GIT installation to git version 
> 2.27.0.windows.1

You're probably going to have a better time here reporting this to the Git for Windows folks at https://github.com/git-for-windows/git.

> I have all my repositories on a NAS and now I get errors with all commands, e.g.
> git status ->  fatal: failed to stat '’: Function not implemented git 
> pull ->  fatal: failed to stat '’: Function not implemented
> 
> Setting fscache to false (globally or locally) does not help. Please 
> fix it quickly 😉

When you report this, you'll need to mention which file system you're using on your NAS, since it's probably related here.  You may also be running into filename length problems and you could try turning on long path support.

Finally, something else you could try is to see if some other process is using these files and if so, kill it.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204


      reply	other threads:[~2020-06-22 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  4:58 AW: Git commands throw error sopq0asmppc9
2020-06-18 17:52 ` brian m. carlson
2020-06-22 16:17   ` sopq0asmppc9 [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='035a01d648b0$a24170d0$e6c45270$@online.de' \
    --to=sopq0asmppc9@online.de \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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