Re: git bundle format

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Nov 26, 2012, 20:56 UTC
Message-ID: <CAMP44s0x17AkYenj8HyXNpkgrPOXtB72dpFOvik882ESohPb7w@mail.gmail.com>
In-Reply-To: <871B6C10EBEFE342A772D1159D13208537ABF676@umechphj.easf.csd.disa.mil>

On Mon, Nov 26, 2012 at 9:50 PM, Pyeron, Jason J CTR (US) <jason.j.pyeron.ctr@mail.mil> wrote:

Show 22 quoted lines

>> -----Original Message-----
>> From: Felipe Contreras
>> Sent: Monday, November 26, 2012 3:20 PM
>>
>> On Mon, Nov 26, 2012 at 8:24 PM, Pyeron, Jason J CTR (US)
>> <jason.j.pyeron.ctr@mail.mil> wrote:
>> > I may need to be nudged in a better direction, but please try to
>> understand my intentions.
>> >
>> > I am facing a situation where I would like to use git bundle but at
>> the same time inspect the contents to prevent a spillage[1].
>> >
> <snip/>
>> >
>> > Am I barking up the right tree?
>>
>> Have you tried 'git fast-export'? The output is definitely not human
>> inspectable, but should be relatively easy to parse to generate such a
>> format. And instead of 'git bundle unbundle' you could use 'git
>> fast-import'. or simply do the conversion in your script.
>
> No. But I am going to read up on it today. It clearly says "You can use it as a human-readable bundle replacement"[4].

Ah, didn't notice that.

> My initial question is does it ever use deltas?

No.

> The repositories I just tested it on only seem to output full blobs (which is really nice from this use case point of view).

In my experience it's nice for most use-cases. Since git only deals with full file contents, that makes sense.

Cheers.

-- 
Felipe Contreras