From: Stefan Beller <stefanbeller@googlemail.com>
To: Andy Lutomirski <luto@amacapital.net>, git@vger.kernel.org
Subject: Re: Verifiable git archives?
Date: Thu, 09 Jan 2014 20:26:32 +0100 [thread overview]
Message-ID: <52CEF7E8.3060100@googlemail.com> (raw)
In-Reply-To: <CALCETrU88evB6VQrE8=8vrc+HYXAX8_Zx7TsYZp6YXeE4dZdvg@mail.gmail.com>
On 09.01.2014 04:10, Andy Lutomirski wrote:
> It's possible, in principle, to shove enough metadata into the output
> of 'git archive' to allow anyone to verify (without cloning the repo)
> to verify that the archive is a correct copy of a given commit. Would
> this be considered a useful feature?
>
Do you know git bundles?
> Presumably there would be a 'git untar' command that would report
> failure if it fails to verify the archive contents.
>
> This could be as simple as including copies of the commit object and
> all relevant tree objects and checking all of the hashes when
> untarring.
>
I thought the git archive rather had the purpose of creating plain
archives not polluted with any gitish stuff.
> (Even better: allow subsets of the repository to be archived and
> verified as well.)
Stefan
next prev parent reply other threads:[~2014-01-09 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 3:10 Verifiable git archives? Andy Lutomirski
2014-01-09 19:26 ` Stefan Beller [this message]
2014-01-09 20:11 ` Junio C Hamano
2014-01-09 20:51 ` Andy Lutomirski
2014-01-09 22:46 ` Junio C Hamano
2014-01-09 22:50 ` Andy Lutomirski
2014-01-19 0:35 ` Michael Haggerty
2014-01-21 19:38 ` Junio C Hamano
2014-01-25 21:56 ` Andy Lutomirski
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=52CEF7E8.3060100@googlemail.com \
--to=stefanbeller@googlemail.com \
--cc=git@vger.kernel.org \
--cc=luto@amacapital.net \
/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).