git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Robert Brown <RBrown@esri.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git issue clone issue with .gdb , .loz, & .las files
Date: Thu, 12 May 2022 15:36:25 +0000	[thread overview]
Message-ID: <SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com> (raw)

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 ®


             reply	other threads:[~2022-05-12 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 15:36 Robert Brown [this message]
2022-05-13  1:49 ` Git issue clone issue with .gdb , .loz, & .las files brian m. carlson

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=SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com \
    --to=rbrown@esri.com \
    --cc=git@vger.kernel.org \
    /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).