From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Alif Wahid <alif.wahid@gmail.com>
Cc: David Fries <david@fries.net>, Nicolas Pitre <nico@fluxnic.net>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: Git exhausts memory.
Date: Tue, 5 Apr 2011 18:13:44 +0700 [thread overview]
Message-ID: <BANLkTi=nzY7wFTr3647SYkSMHx=AityRgw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik6XoWaehp7=5fxwcyhkTHWCO8-Eg@mail.gmail.com>
On Tue, Apr 5, 2011 at 11:35 AM, Alif Wahid <alif.wahid@gmail.com> wrote:
> It seems to me that if "git init" creates a $GIT_DIR/info/attributes
> file by default with a line like "*.gz -delta", then that will disable
> the memory intensive deltra compression plumbing for those special
> cases where people need to track gzip archives (similarly another line
> "*.bz2 -delta" for bzip2 archives and so on). Since these files can't
> supposedly be compressed much more, I think Git ought to have a
> default heuristic to not attempt any compression on them.
I was thinking of very similar thing on my ride home. But I selected
files on size, not extension. With the (hopefully coming soon)
introduction of pathspec magic specifier [1], we can teach git-attr to
express "files that have size in a range [a,b]" (either a or b can be
infinite). The rest is like yours: applying -delta on selected files
then put such a rule with a default range in default template.
[1] http://thread.gmane.org/gmane.comp.version-control.git/169813/focus=169844
--
Duy
next prev parent reply other threads:[~2011-04-05 11:14 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 [this message]
2011-04-05 11:26 ` Alif Wahid
2011-04-05 16:48 ` Holger Hellmuth
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
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='BANLkTi=nzY7wFTr3647SYkSMHx=AityRgw@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=alif.wahid@gmail.com \
--cc=david@fries.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@fluxnic.net \
/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).