From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Lazy clone ideas
Date: Sat, 10 Jun 2006 10:58:41 +0200 [thread overview]
Message-ID: <e6e1jm$tes$1@sea.gmane.org> (raw)
I've started new thread for lazy clone ideas,
splitting from "Figured out how to get Mozilla into git"
Rogan Dawes wrote:
> Here's an idea. How about separating trees and commits from the actual
> blobs (e.g. in separate packs)? My reasoning is that the commits and
> trees should only be a small portion of the overall repository size, and
> should not be that expensive to transfer. (Of course, this is only a
> guess, and needs some numbers to back it up.)
>
> So, a shallow clone would receive all of the tree objects, and all of
> the commit objects, and could then request a pack containing the blobs
> represented by the current HEAD.
That would be _lazy_ clone (with on-demand pack downloading from "master"
full history repository), rather than shallow clone.
I had an idea for having all the commit objects (without all the tree
objects) below the soft-grafts line (beyond the line we cut-off full
history and start being lazy).
> In this way, the user has a history that will show all of the commit
> messages, and would be able to see _which_ files have changed over time
> e.g. gitk would still work - except for the actual file level diff, "git
> log" should also still work, etc
>
> This would also enable other optimisations.
>
> For example, documentation people would only need to get the objects
> under the doc/ tree, and would not need to actually check out the
> source. Git could detect any actual changes by checking whether it has
> the previous blob in its local repository, and whether the file exists
> locally. Creating a patch would obviously require that the person checks
> out the previous version, but one could theoretically commit a new blob
> to a repo without having the previous one (not saying that this would be
> a good idea, of course)
Something akin to CVS's modules, or rather to how CVS modules can be abused?
Something called, I think, partial checkout?
This is a separate idea and I think worth implementing even for full
repository.
> This would probably require Eric Biederman's "direct access to blob"
> patches, I guess, in order to be feasible.
And it would need place to store URI from where to doenload objects
on-demand: perhaps 'remote alternatives'?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next reply other threads:[~2006-06-10 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 8:58 Jakub Narebski [this message]
2006-06-16 22:59 ` Lazy clone ideas Elrond
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='e6e1jm$tes$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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.
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).