All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Leaving large binaries out of the packfile
Date: Thu, 24 Jun 2010 00:32:47 -0600	[thread overview]
Message-ID: <4C22FC0F.1060805@workspacewhiz.com> (raw)
In-Reply-To: <20100610180457.GO14847@spearce.org>

  ----- Original Message -----
From: Shawn O. Pearce
Date: 6/10/2010 12:04 PM
> Joshua Jensen<jjensen@workspacewhiz.com>  wrote:
>> Sometimes, 'git gc' runs out of memory.  I have to discover which file
>> is causing the problem, so I can add it to .gitattributes with a
>> '-delta' flag.  Mostly, though, the repacking takes forever, and I dread
>> running the operation.
> If you have the list of big objects, you can put them into their
> own pack file manually.  Feed their SHA-1 names on stdin to git
> pack-objects, and save the resulting pack under .git/objects/pack.
>
> Assuming the pack was called pack-DEADC0FFEE.pack, create a file
> called pack-DEADC0FFEE.keep in the same directory.  This will stop
> Git from trying to repack the contents of that pack file.
>
> Now run `git gc` to remove those huge objects from the pack file
> that contains all of the other stuff
Pardon the late response.

This method can work, but it is a manual process.  I am interested in a 
method where Git can make the determination for me based on a wildcard 
and flag from .gitattributes.

I am still playing with the feature within a multi-gigabyte repository 
with lots of large binaries.  I'll post more about it when some 
additional changes have been made.

Thanks!

Josh

      parent reply	other threads:[~2010-06-24  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  6:25 Leaving large binaries out of the packfile Joshua Jensen
2010-06-10 18:04 ` Shawn O. Pearce
2010-06-11 15:29   ` Paolo Bonzini
2010-06-11 16:17     ` Shawn O. Pearce
2010-06-24  6:32   ` 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=4C22FC0F.1060805@workspacewhiz.com \
    --to=jjensen@workspacewhiz.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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 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.