Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Avoid spending cycles to deltify binary guck
Date: Sat, 19 May 2007 00:47:59 -0700	[thread overview]
Message-ID: <117956087914-git-send-email-junkio@cox.net> (raw)

Somebody wondered on #git if there is a way to avoid spending
cycles and memory on certain objects in a repository, most
notably huge image files (or it might have been porn video
collection, but I do not recall the details).

Here is a quick-and-clean patch series to help such a repository.

 [PATCH 1/2] pack-objects: pass fullname down to add_object_entry()
 [PATCH 2/2] Teach "delta" attribute to pack-objects.

Although we give pack-objects the pathname for each blob, we
used to hash it down before registering the object to
object_entry array.  The first one moves the call site to the
hash function a bit, to give add_object_entry() to inspect the
pathname.

The second patch teaches add_object_entry() to record if an
entry should be exempt from the deltification process, and use
the .gitattributes mechanism to tell which objects should be
marked as such.

The patches are based on np/pack series, and should apply
cleanly to 'next'.

                 reply	other threads:[~2007-05-19  7:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=117956087914-git-send-email-junkio@cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.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