From: Enrico Weigelt <weigelt@metux.de>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: GIT as binary repository
Date: Fri, 22 Oct 2010 07:02:58 +0200 [thread overview]
Message-ID: <20101022050257.GB27179@nibiru.local> (raw)
In-Reply-To: <AANLkTikk5FA-3LQNfjj6rq0ouO7CywZ9_FaaZCGRM_YB@mail.gmail.com>
* Shawn Pearce <spearce@spearce.org> wrote:
> On Thu, Oct 21, 2010 at 12:54 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> > BTW: how are the current tree objects structured ? Is there always
> > one big tree object representing the whole tree or can it be
> > splitted hierachically ?
>
> Trees in the repository are split hierarchically, but its a flat list
> in the dircache/index file (aka $GIT_DIR/index).
Good. That should allow optimizations for large trees w/o
having to change object formats.
What about splitted blobs ? Is this supported by the object
format right now ?
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2010-10-22 5:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 12:52 GIT as binary repository Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 14:19 ` Tay Ray Chuan
2010-10-21 19:54 ` Enrico Weigelt
2010-10-21 21:23 ` Shawn Pearce
2010-10-22 5:02 ` Enrico Weigelt [this message]
2010-10-22 19:20 ` Shawn Pearce
2010-10-21 17:38 ` Shawn Pearce
2010-10-21 18:53 ` Wilson, Kevin Lee (OpenView Engineer)
2010-10-21 19:19 ` Enrico Weigelt
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=20101022050257.GB27179@nibiru.local \
--to=weigelt@metux.de \
--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).