git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Ingo Wolf <ingo.wolf@gmx.de>
Cc: Git List <git@vger.kernel.org>
Subject: Re: WebDav WorkDir Windows not working
Date: Sun, 27 Oct 2019 17:58:50 +0000	[thread overview]
Message-ID: <20191027175850.b6le5r3jf3cxtnah@camp.crustytoothpaste.net> (raw)
In-Reply-To: <6c355683-726d-c497-d5df-bb7f8ea770d2@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]

On 2019-10-26 at 03:07:39, Ingo Wolf wrote:
> Hi,
> Git Windows somehow does not work with a Webdav Workdir even wenn
> connected to a Drive-Letter.
> It seems like everything work except stat.
> So I can checkout to the Webdav Workdir and all the files are checked out,
> but git status says the files are deleted even still there.
> I can also commit the files, but next git status says deleted again.
> When I checkout the files again checkout says error files exist.
> This is somehow strange.
> Unfortunately I still can't add a not empty worktree, my workaround is
> add the worktree to another dir and then move the .git file and edit
> the dir name in the worktrees/xyz folder.
> But now I have the strange Webdav Problem...

Knowing how WebDAV works under the hood, I'm not entirely surprised that
you're having this problem.  WebDAV is an okay file transfer protocol,
but it's not very good for expressing rich file system semantics.  Git
expects a file system that provides most of the POSIX guarantees, case
sensitivity excepted, and I'm not sure that WebDAV can provide those.

You can try a couple of things which might help.  You can set
core.trustctime to "false" and core.checkStat to "minimal", which may
help with the inconsistent stat information.  It's also possible that
your WebDAV server has a flaky network connection or is nonconformant,
which happens sometimes, so you could try a different WebDAV server
implementation or a different server.

If none of these seem to work, then you'll probably have to come up with
a solution that doesn't involve using repositories or worktrees on a
WebDAV mount.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

  reply	other threads:[~2019-10-27 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26  3:07 WebDav WorkDir Windows not working Ingo Wolf
2019-10-27 17:58 ` brian m. carlson [this message]
2019-11-03 20:37   ` Windows Git Status doesn't see files on WebDav, everything else do Ingo Wolf
2019-11-04 12:29     ` Johannes Schindelin
2019-11-04 13:41       ` Ingo Wolf
2019-11-04 14:22       ` Ingo Wolf
2019-11-04 15:23         ` Kerry, Richard
2019-11-04 16:56           ` Ingo Wolf
2019-11-04 17:35           ` Solved: Windows Git WebDav WorkDir Ingo Wolf

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=20191027175850.b6le5r3jf3cxtnah@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=ingo.wolf@gmx.de \
    /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).