git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: chris@seberino.org
Cc: git@vger.kernel.org
Subject: Re: Curious about details of optimization of object database...
Date: Fri, 9 Jan 2009 09:56:19 -0800	[thread overview]
Message-ID: <20090109175619.GA807@linode.davidb.org> (raw)
In-Reply-To: <20090109174623.GC12552@seberino.org>

On Fri, Jan 09, 2009 at 09:46:23AM -0800, chris@seberino.org wrote:
>I'm told a commit is *not* a patch (diff), but, rather a copy of the entire
>tree.
>
>Can anyone say, in a few sentences, how git avoids needing to keep multiple
>slightly different copies of entire files without just storing lots of
>patches/diffs?

   Documentation/technical/pack-heuristics.txt

David

  parent reply	other threads:[~2009-01-09 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 17:46 Curious about details of optimization of object database chris
2009-01-09 17:55 ` Matthieu Moy
2009-01-09 18:34   ` Nicolas Pitre
2009-01-09 17:56 ` David Brown [this message]
2009-01-09 19:07 ` Boyd Stephen Smith Jr.

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=20090109175619.GA807@linode.davidb.org \
    --to=git@davidb.org \
    --cc=chris@seberino.org \
    --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;
as well as URLs for NNTP newsgroup(s).