From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.14.0-rc1
Date: Wed, 26 Jul 2017 23:28:36 +0000 [thread overview]
Message-ID: <20170726232836.75arz2glmhnzwlc3@genre.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqmv7tbgl4.fsf@gitster.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Mon, Jul 24, 2017 at 03:44:23PM -0700, Junio C Hamano wrote:
> A release candidate Git v2.14.0-rc1 is now available for testing
> at the usual places. It is comprised of 708 non-merge commits
> since v2.13.0, contributed by 61 people, 14 of which are new faces.
>
> The tarballs are found at:
>
> https://www.kernel.org/pub/software/scm/git/testing/
I noticed these tarballs are signed with SHA-1. Since we're working on
adding additional hash support for SHA-256, I was wondering if you might
consider using SHA-256 instead.
This works all the way back to the GnuPG shipped with CentOS 4, so there
should be no compatibility issues. If you're using a reasonably
up-to-date version of GnuPG 1.4 or 2, you should be able to simply drop
the following line in ~/.gnupg/gpg.conf and have things work:
personal-digest-preferences SHA256 SHA384 SHA512
You can also change the order to suit your liking; SHA-384 and SHA-512
support still goes back to at least 2007 (CentOS 5).
--
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
prev parent reply other threads:[~2017-07-26 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 22:44 [ANNOUNCE] Git v2.14.0-rc1 Junio C Hamano
2017-07-26 23:28 ` brian m. carlson [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=20170726232836.75arz2glmhnzwlc3@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).