Re: Possible git bug when working with Microsoft Mapped drives

From: Jeff Hostetler <git@jeffhostetler.com>
Date: Jul 18, 2022, 20:46 UTC
Message-ID: <b5931787-3589-102f-cfeb-caeb8a07e149@jeffhostetler.com>
In-Reply-To: <f946c577-d3d6-212c-cec5-a6c63856b77d@kinzelman.com>

On 7/18/22 4:28 PM, Paul Kinzelman wrote:

Show 20 quoted lines

> I'm using git version 2.37.1.windows.1 and Windows 10
> 
> I've got two systems which are miles apart and so are not on the same
> LAN, and I have connected them together using the ui.com VPN and M$
> RDP/TSclient. I mapped each system's C: drive to be accessed by the
> other system as Drive X: and I can transfer files back and forth
> initiated on each system.
> 
> I can also see all the repository files on the source system, including
> the tree of files under the .git directory. Note I had to unhide the
> .git folder so that I could see that folder from the other system.
> 
> However, when I run 'git clone' on one system to get the repository from
> the other system, git seems to think the repository on the other
> system is empty when it's not. As I said, I can even do a directory
> and see all the other files.
> 
> Any suggestions would be appreciated. Thanks!
> -Paul Kinzelman, Peralta NM
>

I can't duplicate your setup, so I'll just speculate out loud here. I have to wonder if the "X:" drive letters are tricking Git to thinking that the remote instance is actually local and Git is trying to use some shortcuts. (For example, it might hardlink them rather than copy them on Linux.)

So I'm wondering if "--no-local" or "--no-hardlinks" or using a file URL rather than a pathname might make it behave differently.

Again, this is just a guess.

There are also some GIT_TRACE* environment variables that might be helpful if the above doesn't help.

Jeff

https://git-scm.com/docs/git-clone