From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Robert Brown <RBrown@esri.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git issue clone issue with .gdb , .loz, & .las files
Date: Fri, 13 May 2022 01:49:02 +0000 [thread overview]
Message-ID: <Yn23d9UWONDFzH7n@camp.crustytoothpaste.net> (raw)
In-Reply-To: <SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On 2022-05-12 at 15:36:25, Robert Brown wrote:
> Hi team,
Hey,
> 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.
As I mentioned, I think Git LFS is a red herring here. There are no
patterns in .gitattributes, so the fact that it's installed is
irrelevant, since it's not being used.
To summarize what I said on the Git LFS issue tracker, I think you've
seeing a problem with Git on Windows where it doesn't always handle
files larger than 4 GiB properly. My guess is that if you created the
repository in WSL or on a Linux box, things would work, provided you
used a 64-bit binary. Can you try doing that and seeing if cloning to
another Linux-based directory works properly for you in that case?
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2022-05-13 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 15:36 Robert Brown
2022-05-13 1:49 ` brian m. carlson [this message]
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=Yn23d9UWONDFzH7n@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=RBrown@esri.com \
--cc=git@vger.kernel.org \
--subject='Re: Git issue clone issue with .gdb , .loz, & .las files' \
/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
Code repositories for project(s) associated with this 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).