[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] proposed v3 source format using .git.tar.gz

On Sun, Oct 07, 2007 at 02:19:36PM -0500, Manoj Srivastava wrote:
>         Err, and why am I doing this? Why am I not shipping my working
>  directory as a tarball, complete instead of breaking it up
>  (apparently arbitrarily) into three parts?

As opposed to an .orig.tar.gz and all the debian/, {arch}/, and
.arch-ids/ components in the .diff.gz ?

>         How is git reconstituting the files if there is no network
>  access?  Are they shipping all the bits needed to get a full working
>  dir without any network access?

Yes.  the .git/ (or .bzr/ ) directory contains the entire (or abridged
in the case of these shallow clones) history so you can "check out" any
of the covered revisions.

This would be akin to you including a cachedrev of an arbitrary version
followed by all the subsequent patches.tar.gz files, except that I
believe git et al. are meant to be more space-efficient.

Reply to: