From: Holger Hellmuth <hellmuth@ira.uka.de>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Git Mailing List <git@vger.kernel.org>,
Alif Wahid <alif.wahid@gmail.com>
Subject: Re: Git exhausts memory.
Date: Tue, 05 Apr 2011 18:48:18 +0200 [thread overview]
Message-ID: <4D9B47D2.6050909@ira.uka.de> (raw)
In-Reply-To: <BANLkTinU7x16yp+y-HW9UhkVn9SftOJCcA@mail.gmail.com>
On 04.04.2011 16:57, Nguyen Thai Ngoc Duy wrote:
> On Mon, Apr 4, 2011 at 7:52 PM, Alif Wahid<alif.wahid@gmail.com> wrote:
>> Hi Nicolas,
>>
>> On 4 April 2011 01:18, Nicolas Pitre<nico@fluxnic.net> wrote:
>>>
>>> Something you can try is to simply tell Git not to attempt any delta
>>> compression on those tar files using gitattributes (see the man page of
>>> the same name).
>
> Should we change the default to not delta if a blob exceeds predefined
> limit (say 128M)? People who deliberately wants to delta them can
> still set delta attr. 1.8.0 material maybe?
Isn't this already done with the config variable core.bigFileThreshold ?
documentation says: "Files larger than this size are stored deflated,
without attempting delta compression. ... Default is 512 MiB on all
platforms."
next prev parent reply other threads:[~2011-04-05 17:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 5:01 Git exhausts memory Alif Wahid
2011-04-02 15:05 ` Nicolas Pitre
2011-04-03 9:15 ` Alif Wahid
2011-04-03 15:18 ` Nicolas Pitre
2011-04-04 12:52 ` Alif Wahid
2011-04-04 14:57 ` Nguyen Thai Ngoc Duy
2011-04-05 2:22 ` David Fries
2011-04-05 4:35 ` Alif Wahid
2011-04-05 11:13 ` Nguyen Thai Ngoc Duy
2011-04-05 11:26 ` Alif Wahid
2011-04-05 16:48 ` Holger Hellmuth [this message]
2011-04-05 17:06 ` Shawn Pearce
2011-04-05 17:44 ` Junio C Hamano
2011-04-05 20:56 ` Nicolas Pitre
2011-04-05 22:16 ` Junio C Hamano
2011-04-05 22:19 ` Shawn Pearce
2011-04-06 0:34 ` Nicolas Pitre
2011-04-06 15:51 ` Jay Soffian
2011-04-06 16:33 ` Junio C Hamano
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=4D9B47D2.6050909@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=alif.wahid@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pclouds@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 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.