From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Alexander Miseler <alexander@miseler.de>,
Eric Montellese <emontellese@gmail.com>,
Pete Wyckoff <pw@padd.com>,
git@vger.kernel.org, schacon@gmail.com, joey@kitenet.net
Subject: Re: Fwd: Git and Large Binaries: A Proposed Solution
Date: Wed, 16 Mar 2011 21:40:51 +0700 [thread overview]
Message-ID: <AANLkTintr3szKMhbegeUgu+KHGtBGTRyQ3Y4pOwfwhEr@mail.gmail.com> (raw)
In-Reply-To: <20110314193254.GA21581@sigill.intra.peff.net>
On Tue, Mar 15, 2011 at 2:32 AM, Jeff King <peff@peff.net> wrote:
> That being said, I'm not sure how much this optimization will buy us.
> There are times when being able to mmap() the file directly, or point an
> external program directly at the original blob will be helpful. But we
> will still have to copy, for example on checkout.
Sparse checkout code may help. If those large files are not always
needed, they can be marked skip-checkout based on
core.bigFileThreshold and won't be checked out until explictly
requested. This use may conflict with sparse checkout because it sets
skip-checkout bits automatically from $GIT_DIR/info/sparsecheckout
though.
--
Duy
next prev parent reply other threads:[~2011-03-16 14:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin=UySutWLS0Y7OmuvkE=T=+YB8G8aUCxLH=GKa@mail.gmail.com>
2011-01-21 18:57 ` Fwd: Git and Large Binaries: A Proposed Solution Eric Montellese
2011-01-21 21:36 ` Wesley J. Landaker
2011-01-21 22:00 ` Eric Montellese
2011-01-21 22:24 ` Jeff King
2011-01-21 23:15 ` Eric Montellese
2011-01-22 3:05 ` Sverre Rabbelier
2011-01-23 14:14 ` Pete Wyckoff
2011-01-26 3:42 ` Scott Chacon
2011-01-26 16:23 ` Eric Montellese
2011-01-26 17:42 ` Joey Hess
2011-01-26 21:40 ` Jakub Narebski
2011-03-10 21:02 ` Alexander Miseler
2011-03-10 22:24 ` Jeff King
2011-03-13 1:53 ` Eric Montellese
2011-03-13 2:52 ` Jeff King
2011-03-13 19:33 ` Alexander Miseler
2011-03-14 19:32 ` Jeff King
2011-03-16 0:35 ` Eric Montellese
2011-03-16 14:40 ` Nguyen Thai Ngoc Duy [this message]
2011-01-22 0:07 ` Joey Hess
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=AANLkTintr3szKMhbegeUgu+KHGtBGTRyQ3Y4pOwfwhEr@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=alexander@miseler.de \
--cc=emontellese@gmail.com \
--cc=git@vger.kernel.org \
--cc=joey@kitenet.net \
--cc=peff@peff.net \
--cc=pw@padd.com \
--cc=schacon@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.
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).