From: Jakub Narebski <jnareb@gmail.com>
To: Nick Triantos <nick@perceptivepixel.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Roadmap to better handle big files?
Date: Wed, 24 Feb 2010 15:51:00 -0800 (PST) [thread overview]
Message-ID: <m3fx4qmbwr.fsf@localhost.localdomain> (raw)
In-Reply-To: <B85968F5-E7C2-499D-A8BE-0160BA575F10@perceptivepixel.com>
Nick Triantos <nick@perceptivepixel.com> writes:
> Is there any planned functionality to better support large files in
> git? (> 100MB / file)
>
> We've been happily using git but we now have some files which we'd
> very much like to have under the same version control as our source
> code, and some of those files have been as large as 450MB/file. We
> are looking at chunking the file up before commiting it to git, but
> is there any plan to better support chunking of these files during
> repacks or other operations? Right now, it appears either the whole
> file, or the whole collection of files in a commit (not sure which)
> can need to be resident in memory up to twice, from reading various
> places on the web. Our poor 32-bit server is barfing on this. We
> are going to put more RAM and a 64bit OS on the machine, but this
> still seems like an unnecessary design decision.
Git has a roadmap???
More seriously, take a look at git-bigfiles project (fork):
http://caca.zoy.org/wiki/git-bigfiles
HTH
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-02-24 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 23:00 Roadmap to better handle big files? Nick Triantos
2010-02-24 23:39 ` Nicolas Pitre
2010-02-24 23:51 ` Jakub Narebski [this message]
2010-02-25 0:02 ` Nick Triantos
2010-02-25 18:06 ` Joshua Jensen
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=m3fx4qmbwr.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=nick@perceptivepixel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.