From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [ANNOUNCE] Git v2.21.0-rc2
Date: Thu, 21 Feb 2019 20:10:00 +0700 [thread overview]
Message-ID: <CACsJy8D=-+TqZSf1oyTJs_O+=KAV66OE_As5cTKXxHoXAhzkGw@mail.gmail.com> (raw)
In-Reply-To: <xmqqftsiw8l8.fsf@gitster-ct.c.googlers.com>
On Thu, Feb 21, 2019 at 2:41 AM Junio C Hamano <gitster@pobox.com> wrote:
> Another mention of /dev/zero appears in t/helper/test-sha1.sh (not
> to be confused with t/helper/test-sha1.c). This seems to be run
> only with an explicit "make -C t/helper check-sha1" request, so
> perhaps nobody on your platform ran it to get hit by it. I wonder
> if anybody runs this on any platform, to be honest, though.
I vaguely remember Brian added something to test SHA-512 performance
but I can't find it. Maybe when he adds something (if it's not there
already) we can retire this script, or update it to check sha-512 too.
> Duy Cc'ed as the last person to touch that particular target---yes, I
> know I was guilty of introducing it in b65bc21e ("Makefile: add
> framework to verify and bench sha1 implementations.", 2006-06-24).
--
Duy
next prev parent reply other threads:[~2019-02-21 13:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 23:29 [ANNOUNCE] Git v2.21.0-rc2 Junio C Hamano
2019-02-20 0:43 ` Randall S. Becker
2019-02-20 19:41 ` Junio C Hamano
2019-02-20 20:46 ` Johannes Schindelin
2019-02-21 13:10 ` Duy Nguyen [this message]
2019-02-21 23:55 ` brian m. carlson
2019-02-22 9:13 ` Duy Nguyen
2019-02-21 15:54 ` Randall S. Becker
2019-02-21 20:04 ` Junio C Hamano
2019-02-21 21:06 ` SZEDER Gábor
2019-02-21 21:30 ` Randall S. Becker
2019-02-21 19:59 ` Randall S. Becker
2019-02-21 10:46 ` Git for Windows v2.21.0-rc2, was " Johannes Schindelin
2019-02-21 19:28 ` [PATCH 0/2] BSD portability fixes for 2.21.0-rc2 Ævar Arnfjörð Bjarmason
2019-02-22 0:37 ` Josh Steadmon
2019-02-21 19:28 ` [PATCH 1/2] tests: fix unportable "\?" and "\+" regex syntax Ævar Arnfjörð Bjarmason
2019-02-22 5:00 ` Junio C Hamano
2019-02-21 19:28 ` [PATCH 2/2] commit-graph tests: fix cryptic unportable "dd" invocation Ævar Arnfjörð Bjarmason
2019-02-21 20:43 ` SZEDER Gábor
2019-02-21 22:26 ` Ævar Arnfjörð Bjarmason
2019-02-22 10:50 ` SZEDER Gábor
2019-02-22 14:34 ` Ævar Arnfjörð Bjarmason
2019-02-22 18:30 ` Junio C Hamano
2019-02-22 18:35 ` Todd Zullinger
2019-02-22 19:23 ` [PATCH v3] commit-graph tests: fix " Junio C Hamano
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='CACsJy8D=-+TqZSf1oyTJs_O+=KAV66OE_As5cTKXxHoXAhzkGw@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=rsbecker@nexbridge.com \
--cc=sandals@crustytoothpaste.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.
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).