Re: full kernel history, in patchset format

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Apr 16, 2005, 20:19 UTC
Message-ID: <Pine.LNX.4.21.0504161546120.30848-100000@iabervon.org>
In-Reply-To: <42616A9F.1030302@timesys.com>

On Sat, 16 Apr 2005, Mike Taht wrote:

Show 19 quoted lines

> Junio C Hamano wrote:
> >>>>>>"MT" == Mike Taht <mike.taht@timesys.com> writes:
> > 
> > 
> > MT> alternatively, "git-archive-torrent" to create a list of files for a
> > MT> bittorrent feed....
> > 
> > That is certainly good for establishing the baseline, but you
> > still need to leverage the inherent delta-compressibility
> > between related blobs/trees by also doing something like what I
> > described as "diff package", don't you?
> 
> Yes... yes you could have files and diffs generated statically...
> 
> although something like a bittorrent server/client/frontend, call it 
> "gittorrent" (I hate being the first to make this pun) could walk the 
> hashes dynamically (
> Ihave: sha,sha,sha,sha... Sendme: shaxxxxxxxxxxxxxxxxxxx
> Hereswhatyouneedfromgit: file,file,file,diff,diff,diff,...)

I'm actually working on a trivial HTTP client to do this. The user says "get <commit-id> from <url>", and it gets that object, the associated trees, and the associated blobs, skipping any that it already has.

This should save having a non-standard public-facing server process, and be essentially as effective, at least once I have it using a single connection for everything.

	-Daniel
*This .sig left intentionally blank*