From: Colin Walters <walters@verbum.org>
To: git@vger.kernel.org
Subject: Re: weaning distributions off tarballs: extended verification of git tags
Date: Wed, 08 Jul 2015 00:00:49 -0400 [thread overview]
Message-ID: <1436328049.1937003.317969577.6CBA24A0@webmail.messagingengine.com> (raw)
In-Reply-To: <1425134885.3150003.233627665.2E48E28B@webmail.messagingengine.com>
On Sat, Feb 28, 2015, at 10:48 AM, Colin Walters wrote:
> Hi,
>
> TL;DR: Let's define a standard for embedding stronger checksums in tags and commit messages:
> https://github.com/cgwalters/homegit/blob/master/bin/git-evtag
[time passes]
I finally had a bit of time to pick this back up again in:
https://github.com/cgwalters/git-evtag
It should address the core concern here about stability of `git archive`.
I prototyped it out with libgit2 because it was easier, and I'd like actually to be able to use this with older versions of git.
But I think the next steps here are:
- Validate the core design
* Tree walking order
* Submodule recursion
* Use of SHA512
- Standardize it
(Would like to see at least a stupid slow shell script implementation to cross-validate)
- Add it as an option to `git tag`?
Longer term:
- Support adding `Git-EVTag` as a git note, so I can retroactively add stronger
checksums to older git repositories
- Anything else?
prev parent reply other threads:[~2015-07-08 4:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 14:48 weaning distributions off tarballs: extended verification of git tags Colin Walters
2015-02-28 19:14 ` brian m. carlson
2015-02-28 20:34 ` Morten Welinder
2015-03-02 17:09 ` Colin Walters
2015-03-02 18:12 ` Joey Hess
2015-03-02 19:38 ` Sam Vilain
2015-03-02 20:08 ` Junio C Hamano
2015-03-02 20:52 ` Sam Vilain
2015-03-02 23:20 ` Duy Nguyen
2015-03-02 23:44 ` Junio C Hamano
2015-03-03 0:42 ` Duy Nguyen
2015-03-05 12:36 ` Michael Haggerty
2015-07-08 4:00 ` Colin Walters [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1436328049.1937003.317969577.6CBA24A0@webmail.messagingengine.com \
--to=walters@verbum.org \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).