Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jonathan Blanton <jonathan.blanton@gmail.com>, git@vger.kernel.org
Subject: Re: malloc fails when dealing with huge files
Date: Thu, 11 Dec 2008 10:11:04 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0812111009460.18321@eeepc-johanness> (raw)
In-Reply-To: <alpine.LFD.2.00.0812101121401.3340@localhost.localdomain>

Hi,

On Wed, 10 Dec 2008, Linus Torvalds wrote:

> However, git performance with big files would never be wonderful, and 
> things like "git diff" would still end up reading not just the whole 
> file, but _both_versions_ at the same time. Marking the big files as 
> being no-diff might help, though.

Makes me wonder if we should not have a default cut-off, say, 10MB, at 
which files are automatically tagged with the no-diff attribute (unless 
overridden explicitely in .gitattributes)?

Ciao,
Dscho

      parent reply	other threads:[~2008-12-11  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 15:42 malloc fails when dealing with huge files Jonathan Blanton
2008-12-10 19:32 ` Linus Torvalds
2008-12-11  0:16   ` Jeff Whiteside
2008-12-11  9:11   ` Johannes Schindelin [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=alpine.DEB.1.00.0812111009460.18321@eeepc-johanness \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jonathan.blanton@gmail.com \
    --cc=torvalds@linux-foundation.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