Git issue clone issue with .gdb , .loz, & .las files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi team,

I started a thread in GitHub, but they pointed me to you. We're having a binary comparison problems when cloning a repo in Git on Windows (git version 2.36.1.windows.1), LFS is installed but is not tracking files. 

So far we have noticed  .gdb, .las, and .loz files are not even close to the same size and don't open after cloning the repo. Everything else seems to clone fine at the moment, confidence to moving to Git is a problem because of this on the team. I'm looking to figure out a way to make sure we are getting binary matched clones when doing so. We sure would appreciate any help you can give us.  

We are currently testing locally, the repo and the clone exist on the same physical PC
Windows 20H2 (OS Build 19042.1645)
git version 2.36.1.windows.1 (64bit)
git-lfs/3.1.4 (GitHub; windows amd64; go 1.17.8)

Original GitHub Thread
https://github.com/git-lfs/git-lfs/discussions/5005

Robert Brown | Sr. Performance Engineer
Esri | 380 New York Street | Redlands, CA 92373 | USA
T (909) 793-2853 x6618 | mailto:rbrown@xxxxxxxx | http://www.esri.com/ 

THE SCIENCE OF WHERE ®





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux