git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
RBRobert Brown <rbrown@esri.com>
Date
May 12, 2022, 15:36 UTC
Message-ID
<SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com>
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@esri.com | http://www.esri.com/ 

THE SCIENCE OF WHERE ®
Next: brian m. carlson
Message 1 of 2 in “Git issue clone issue with .gdb , .loz, & .las files”
  1. Robert BrownMay 12, 2022
  2. brian m. carlsonMay 13, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.