From: Junio C Hamano <gitster@pobox.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: git@vger.kernel.org
Subject: Re: Verifiable git archives?
Date: Thu, 09 Jan 2014 14:46:44 -0800 [thread overview]
Message-ID: <xmqq38kwai3v.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CALCETrXTbvHQAWm2z13OwyHCmBZZNDSqyWCdiu6maHRp2mi-Pw@mail.gmail.com> (Andy Lutomirski's message of "Thu, 9 Jan 2014 12:51:22 -0800")
Andy Lutomirski <luto@amacapital.net> writes:
>> You only need the object name of the top-level tree. After "untar"
>> the archive into an empty directory, make it a new repository and
>> "git add . && git write-tree"---the result should match the
>> top-level tree the archive was supposed to contain.
>
> Hmm. I didn't realize that there was enough metadata in the 'git
> archive' output to reproduce the final tree.
We do record the commit object name in the extended header when
writing a tar archive already, but you have to grab the commit
object from somewhere in order to read the top-level tree object
name, which we do not record.
Also, if you used keyword substitution and such when creating an
archive, then the filesystem entities resulting from expanding it
would not match the original.
next prev parent reply other threads:[~2014-01-09 22:46 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
2014-01-09 20:11 ` Junio C Hamano
2014-01-09 20:51 ` Andy Lutomirski
2014-01-09 22:46 ` Junio C Hamano [this message]
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=xmqq38kwai3v.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.