From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Pyeron, Jason J CTR (US)" <jason.j.pyeron.ctr@mail.mil>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git bundle format
Date: Mon, 26 Nov 2012 21:56:14 +0100 [thread overview]
Message-ID: <CAMP44s0x17AkYenj8HyXNpkgrPOXtB72dpFOvik882ESohPb7w@mail.gmail.com> (raw)
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:
>> -----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
next prev parent reply other threads:[~2012-11-26 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 19:24 git bundle format Pyeron, Jason J CTR (US)
2012-11-26 19:31 ` Pyeron, Jason J CTR (US)
2012-11-26 20:20 ` Felipe Contreras
2012-11-26 20:50 ` Pyeron, Jason J CTR (US)
2012-11-26 20:56 ` Felipe Contreras [this message]
2012-11-26 20:38 ` Junio C Hamano
2012-11-26 20:53 ` Pyeron, Jason J CTR (US)
2012-11-26 20:56 ` Stephen Bash
2012-11-26 21:06 ` git bundle format [OT] Pyeron, Jason J CTR (US)
2012-11-26 21:31 ` Stephen Bash
2012-11-26 23:08 ` git bundle format Andrew Ardill
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=CAMP44s0x17AkYenj8HyXNpkgrPOXtB72dpFOvik882ESohPb7w@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jason.j.pyeron.ctr@mail.mil \
/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).