From: John Wyzer <john.wyzer@gmx.de>
To: git@vger.kernel.org
Subject: Re: Resumable clone/Gittorrent (again) - stable packs?
Date: Mon, 10 Jan 2011 17:39:31 +0100 [thread overview]
Message-ID: <4D2B3643.2070106@gmx.de> (raw)
In-Reply-To: <AANLkTinc12H01Us1mkKieZo75hwjgTCZth_wFvRNscMq@mail.gmail.com>
On 06/01/11 18:05, Shawn Pearce wrote:
> On Wed, Jan 5, 2011 at 18:29, Zenaan Harkness<zen@freedbms.net> wrote:
>> Bittorrent requires some stability around torrent files.
>>
>> Can packs be generated deterministically?
>
I hope that I don't get something technically wrong (did not read any
code, only skimmed the docs) and that this question is not redundant:
Why not provide an alternative mode for the git:// protocoll that
instead of retrieving a big packaged blob breaks this down to the
smallest atomic objects from the repository? Those are not changing and
should be able to survive partial transfers.
While this might not be as efficient network traffic-wise it would
provide a solution for those behind breaking connections.
next prev parent reply other threads:[~2011-01-10 16:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 2:29 Resumable clone/Gittorrent (again) - stable packs? Zenaan Harkness
2011-01-06 17:05 ` Shawn Pearce
2011-01-10 16:39 ` John Wyzer [this message]
2011-01-10 21:42 ` Sam Vilain
2011-01-11 0:03 ` Nguyen Thai Ngoc Duy
2011-01-11 0:57 ` J.H.
2011-01-11 1:56 ` Nguyen Thai Ngoc Duy
2011-01-06 21:09 ` Nicolas Pitre
2011-01-07 2:36 ` Zenaan Harkness
2011-01-07 4:33 ` Nicolas Pitre
2011-01-07 5:22 ` Jeff King
2011-01-07 5:31 ` Jeff King
2011-01-07 10:04 ` Zenaan Harkness
2011-01-07 18:52 ` Ilari Liusvaara
2011-01-07 19:17 ` Jeff King
2011-01-07 21:45 ` Ilari Liusvaara
2011-01-07 21:56 ` Jeff King
2011-01-07 22:21 ` Ilari Liusvaara
2011-01-07 22:27 ` Jeff King
2011-01-10 21:07 ` Sam Vilain
2011-01-10 11:48 ` Nguyen Thai Ngoc Duy
2011-01-10 13:50 ` 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=4D2B3643.2070106@gmx.de \
--to=john.wyzer@gmx.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).