git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Jensen <jjensen@workspacewhiz.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: Thu, 25 Feb 2010 11:06:10 -0700	[thread overview]
Message-ID: <4B86BC12.9080201@workspacewhiz.com> (raw)
In-Reply-To: <B85968F5-E7C2-499D-A8BE-0160BA575F10@perceptivepixel.com>

----- Original Message -----
From: Nick Triantos
Date: 2/24/2010 4:00 PM
> Is there any planned functionality to better support large files in git?  (>  100MB / file)
>    
I once used Git alternates to point to a network share filled with the 
really large files hashed into a .git/objects directory.  It worked, 
although it was slower than having the entire repository locally.

Josh

      parent reply	other threads:[~2010-02-25 18:13 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
2010-02-25  0:02   ` Nick Triantos
2010-02-25 18:06 ` Joshua Jensen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B86BC12.9080201@workspacewhiz.com \
    --to=jjensen@workspacewhiz.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 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).