From: "Luck, Tony" <tony.luck@intel.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>, "Petr Baudis" <pasky@ucw.cz>
Cc: "Brad Roberts" <braddr@puremagic.com>, <git@vger.kernel.org>
Subject: RE: [3/5] Add http-pull
Date: Fri, 22 Apr 2005 16:34:35 -0700 [thread overview]
Message-ID: <B8E391BBE9FE384DAA4C5C003888BE6F03541C6E@scsmsx401.amr.corp.intel.com> (raw)
>But if you download 1000 files of the 1010 you need, and then your network
>goes down, you will need to download those 1000 again when it comes back,
>because you can't save them unless you have the full history.
So you could make the temporary object repository persistant between pulls
to avoid reloading them across the wire. Something like:
get_commit(sha1)
{
if (sha1 in real_repo) -> done
if (!(sha1 in tmp_repo))
load sha1 to tmp_repo
get_tree(sha1->tree)
for each parent
get_commit(sha1->parent)
move sha1 from tmp_repo to real_repo
}
get_tree(sha1)
{
if (sha1 in real_repo) -> done
if (!(sha1 in tmp_repo))
load sha1 to tmp repo
for_each (sha1->entry) {
case blob: if (!sha1 in real_repo) load to real_repo
case tree: get_tree()
}
move sha1 from tmp_repo to real_repo
}
The "load sha1 to xxx_repo" needs to be smarter than my dumb wget
based script ... it must confirm the sha1 of the object being loaded
before installing (even into the tmp_repo).
-Tony
next reply other threads:[~2005-04-22 23:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 23:34 Luck, Tony [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-17 15:20 [0/5] Patch set for various things Daniel Barkalow
2005-04-17 15:31 ` [3/5] Add http-pull Daniel Barkalow
2005-04-17 18:10 ` Petr Baudis
2005-04-17 18:49 ` Daniel Barkalow
2005-04-17 19:08 ` Petr Baudis
2005-04-17 19:24 ` Daniel Barkalow
2005-04-17 19:59 ` Petr Baudis
2005-04-21 3:27 ` Brad Roberts
2005-04-21 4:28 ` Daniel Barkalow
2005-04-21 22:05 ` tony.luck
2005-04-22 19:46 ` Daniel Barkalow
2005-04-22 22:40 ` Petr Baudis
2005-04-22 23:00 ` Daniel Barkalow
2005-04-22 23:08 ` Petr Baudis
2005-04-22 23:12 ` Daniel Barkalow
2005-04-22 23:24 ` Martin Schlemmer
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=B8E391BBE9FE384DAA4C5C003888BE6F03541C6E@scsmsx401.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=barkalow@iabervon.org \
--cc=braddr@puremagic.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).