From: Philip Oakley <philipoakley@iee.email>
To: Andreas Kalz <andreas-kalz@gmx.de>, git@vger.kernel.org
Subject: Re: Git as data archive
Date: Sat, 7 Dec 2019 16:54:37 +0000 [thread overview]
Message-ID: <60945f9c-d79c-7806-0c5e-3e2affcea001@iee.email> (raw)
In-Reply-To: <21fcdc5f-955a-e027-0d71-15f476f6162c@gmx.de>
Hi Andreas,
On 06/12/2019 18:54, Andreas Kalz wrote:
> Hello,
> I am using git as archive and versioning also for photos. Apart from
> performance issues, I wanted to ask if there are hard limits and
> configurable limits (how to configure?) for maximum single file size and
> maximum .git archive size (Windows 64 Bit system)?
> Thanks in advance for your answer.
> All the best,
> Andreas
On Git the file size is currently limited to size of `long`, rather than
`size_t`. Hence on Git-for Windows the size limit is 32bit ~4GiB
Any change will be a big change as it ripples through many places in the
code base and, for some, will feel 'wrong'. I did some work [1-4] on top
of those of many others that was almost there, but...
The alternative is git-lfs, which I don't personally use (see [4]).
Philip
[1] https://github.com/git-for-windows/git/pull/2179
[2] https://github.com/gitgitgadget/git/pull/115
[3] https://github.com/git-for-windows/git/issues/1063
[4] https://github.com/git-lfs/git-lfs/issues/2434
next prev parent reply other threads:[~2019-12-07 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 18:54 Git as data archive Andreas Kalz
2019-12-07 16:54 ` Philip Oakley [this message]
2019-12-07 18:04 ` Thomas Braun
2019-12-08 18:44 ` Andreas Kalz
2019-12-09 1:18 ` Thomas Braun
2019-12-09 16:39 ` Andreas Kalz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60945f9c-d79c-7806-0c5e-3e2affcea001@iee.email \
--to=philipoakley@iee.email \
--cc=andreas-kalz@gmx.de \
--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.
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 NNTP newsgroup(s).