From: Joey Hess <joey@kitenet.net>
To: Qingning Huo <qingninghuo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: out of memory error with git push and pull
Date: Thu, 2 Jun 2011 00:46:03 -0400 [thread overview]
Message-ID: <20110602044603.GB5081@gnu.kitenet.net> (raw)
In-Reply-To: <BANLkTin3-XnVsVd1-CAiWDBzQG6m=a4Rvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
Qingning Huo wrote:
> I tried to use git to manage my digital photos but encountered some
> problems. The typical file sizes are hundreds of KB or a few MB. In
> total, about 15GB data in about 10,000 files. My intention is to get
> them into a git repository and cloned into a few computers. Probably I
> will make some occasionally changes like editing and deleting. But I
> think most of the files would stay at version one.
I try not to mention git-annex too much here, but this is a perfect
use-case for it. http://git-annex.branchable.com/
Well, it would be more perfect if you had enough data in your repo that
you didn't necessarily want to clone it all to every computer. Like so:
# git annex status
local annex size: 58 megabytes
total annex keys: 38158
total annex size: 6 terabytes
:)
> I wonder whether anyone has tried using git in a similar scenario. Is
> git capable of handling this kind of data? And, are there any settings
> and/or command line options that I should use? I had a quick look of
> git help push (and pull/fetch) but cannot see anything obvious.
There is a tunable you can use to improve things, see core.bigFileThreshold
That originally came from this project.
http://caca.zoy.org/wiki/git-bigfiles -- it may have some other
improvements that have not landed in git, I'm not sure.
--
see shy jo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-06-02 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 22:33 out of memory error with git push and pull Qingning Huo
2011-06-02 4:46 ` Joey Hess [this message]
2011-06-02 22:13 ` Qingning Huo
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=20110602044603.GB5081@gnu.kitenet.net \
--to=joey@kitenet.net \
--cc=git@vger.kernel.org \
--cc=qingninghuo@gmail.com \
/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).