From: "Jon Smirl" <jonsmirl@gmail.com>
To: "David Tweed" <david.tweed@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Calculating tree nodes
Date: Tue, 4 Sep 2007 01:52:05 -0400 [thread overview]
Message-ID: <9e4733910709032252x1fe6f436wdd13bcb1a6f76636@mail.gmail.com> (raw)
In-Reply-To: <e1dab3980709032119r381f7a91ia84ba09039c21be1@mail.gmail.com>
On 9/4/07, David Tweed <david.tweed@gmail.com> wrote:
> On 9/4/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > Git has picked up the hierarchical storage scheme since it was built
> > on a hierarchical file system.
>
> FWIW my memory is that initial git used path-to-blob lists (as you're
> describing but without delta-ing) and tree nodes were added after a
> couple of weeks, the motivation _at the time_ being they were a
> natural way to dramatically reduce the size of repos.
>
> One of the nice things about tree nodes is that for doing a diff
> between versions you can, to overwhelming probability, decide
> equality/inequality of two arbitrarily deep and complicated subtrees
> by comparing 40 characters, regardless of how remote and convoluted
> their common ancestry. With delta chains don't you end up having to
> trace back to a common "entry" in the history? (Of course, I don't
> know how packs affect this - presumably there's some delta chasing to
> get to the bare objects as well.)
While it is a 40 character compare, how many disk accesses were needed
to get those two SHAs into memory?
>
> --
> cheers, dave tweed__________________________
> david.tweed@gmail.com
> Rm 124, School of Systems Engineering, University of Reading.
> "we had no idea that when we added templates we were adding a Turing-
> complete compile-time language." -- C++ standardisation committee
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-09-04 5:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 2:13 Calculating tree nodes Jon Smirl
2007-09-04 2:51 ` Shawn O. Pearce
2007-09-04 3:26 ` Jon Smirl
2007-09-04 3:40 ` Johannes Schindelin
2007-09-04 3:54 ` Jon Smirl
2007-09-04 4:21 ` Martin Langhoff
2007-09-04 5:37 ` Jon Smirl
2007-09-04 5:51 ` Andreas Ericsson
2007-09-04 10:33 ` Johannes Schindelin
2007-09-04 14:31 ` Jon Smirl
2007-09-04 15:05 ` Johannes Schindelin
2007-09-04 15:14 ` Andreas Ericsson
2007-09-04 21:02 ` Martin Langhoff
2007-09-04 4:28 ` Junio C Hamano
2007-09-04 5:50 ` Jon Smirl
2007-09-04 4:19 ` David Tweed
2007-09-04 5:52 ` Jon Smirl [this message]
2007-09-04 5:55 ` Andreas Ericsson
2007-09-04 6:16 ` Shawn O. Pearce
2007-09-04 14:19 ` Jon Smirl
2007-09-04 14:41 ` Andreas Ericsson
2007-09-04 6:16 ` David Tweed
2007-09-04 6:26 ` Shawn O. Pearce
2007-09-04 17:39 ` Junio C Hamano
2007-09-06 3:20 ` Shawn O. Pearce
2007-09-06 5:21 ` Junio C Hamano
2007-09-04 16:20 ` Daniel Hulme
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=9e4733910709032252x1fe6f436wdd13bcb1a6f76636@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=david.tweed@gmail.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.
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).