From: Chris Mason <mason@suse.com>
To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] packed delta git
Date: Thu, 19 May 2005 14:53:21 -0400 [thread overview]
Message-ID: <200505191453.21566.mason@suse.com> (raw)
In-Reply-To: <20050519183810.GF8105@cip.informatik.uni-erlangen.de>
On Thursday 19 May 2005 14:38, Thomas Glanzmann wrote:
> Hello Chris,
>
> > size (du -sh .git) 2.5G 227M
>
> wow that beats bitkeeper in size. What is missing to actual use such a
> approach in a distributed environment?
It's not quite fair to compare with bitkeeper, since my changeset comments are
only the name of the bk->cvs patch, and I've only got 28k changesets vs bk's
60k or so.
In terms of actually making use of this, we need to deal with the hard linked
files during push/pull. This means using -H on rsync and teaching the
push/pull code about packed files.
git-pack needs to be able to unpack/undelta files so that people can clean a
tree.
git-fsck-cache needs to understand packed files and deltas.
-chris
next prev parent reply other threads:[~2005-05-19 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 22:57 [PATCH] packed delta git Chris Mason
2005-05-19 18:28 ` Chris Mason
2005-05-19 18:38 ` Thomas Glanzmann
2005-05-19 18:53 ` Chris Mason [this message]
2005-05-19 19:30 ` Nicolas Pitre
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=200505191453.21566.mason@suse.com \
--to=mason@suse.com \
--cc=git@vger.kernel.org \
--cc=sithglan@stud.uni-erlangen.de \
/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).