From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Colin Walters <walters@verbum.org>
Cc: git@vger.kernel.org
Subject: Re: upstreaming https://github.com/cgwalters/git-evtag ?
Date: Mon, 8 Jan 2018 21:34:45 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1801082132510.31@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (raw)
In-Reply-To: <1515442320.3241451.1228399576.66D7DA96@webmail.messagingengine.com>
Hi,
On Mon, 8 Jan 2018, Colin Walters wrote:
> Hi, so quite a while ago I wrote this:
> https://github.com/cgwalters/git-evtag
For the benefit of readers who prefer to stay in their mail readers:
git-evtag
git-evtag can be used as a replacement for git-tag -s. It will
generate a strong checksum (called Git-EVTag-v0-SHA512) over the
commit, tree, and blobs it references (and recursively over
submodules). A primary rationale for this is that the underlying SHA1
algorithm of git is under increasing threat. Further, a goal here
is to create a checksum that covers the entire source of a single
revision as a replacement for tarballs + checksums.
> Since I last posted about this on the list here, of course
> shattered.io happened. It also looks
> like there was a node.js implementation written.
>
> Any interest in having this in core git?
I have no opinion, I was just curious what this otherwise undescribed
thing was about.
Ciao,
Johannes
next prev parent reply other threads:[~2018-01-08 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 20:12 upstreaming https://github.com/cgwalters/git-evtag ? Colin Walters
2018-01-08 20:34 ` Johannes Schindelin [this message]
2018-01-08 20:40 ` Santiago Torres
2018-01-08 20:42 ` Colin Walters
2018-01-08 20:51 ` Santiago Torres
2018-01-08 20:49 ` Stefan Beller
2018-01-08 20:54 ` Santiago Torres
2018-01-09 2:30 ` Colin Walters
2018-01-09 18:09 ` Santiago Torres
2018-01-09 20:38 ` Jonathan Nieder
2018-01-10 16:38 ` Santiago Torres
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=nycvar.QRO.7.76.6.1801082132510.31@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=walters@verbum.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).