From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH] mingw: use OpenSSL's SHA-1 routines
Date: Thu, 09 Feb 2017 15:41:51 -0800 [thread overview]
Message-ID: <xmqqbmublyo0.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <6a29f8c60d315a24292c1fa9f5e84df4dfdbf813.1486679254.git.johannes.schindelin@gmx.de> (Johannes Schindelin's message of "Thu, 9 Feb 2017 23:27:49 +0100 (CET)")
Johannes Schindelin <johannes.schindelin@gmx.de> writes:
> From: Jeff Hostetler <jeffhost@microsoft.com>
>
> Use OpenSSL's SHA-1 routines rather than builtin block-sha1 routines.
> This improves performance on SHA1 operations on Intel processors.
> ...
>
> Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
Nice. Will queue as jh/mingw-openssl-sha1 topic; it is a bit too
late for today's integration cycle to be merged to 'next', but let's
have this by the end of the week in 'master'.
Thanks.
next prev parent reply other threads:[~2017-02-09 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 22:27 [PATCH] mingw: use OpenSSL's SHA-1 routines Johannes Schindelin
2017-02-09 23:41 ` Junio C Hamano [this message]
2017-02-11 8:01 ` Johannes Sixt
2017-02-11 18:51 ` Junio C Hamano
2017-02-13 17:16 ` Johannes Schindelin
2017-02-16 18:12 ` Johannes Sixt
2017-02-10 5:02 ` Jeff King
2017-02-10 15:49 ` Johannes Schindelin
2017-02-10 16:04 ` Jeff King
2017-02-13 17:46 ` Johannes Sixt
2017-02-13 19:42 ` Junio C Hamano
2017-02-13 21:07 ` Johannes Sixt
2017-02-13 22:38 ` Johannes Schindelin
2017-02-14 6:14 ` Johannes Sixt
2017-02-24 21:54 ` Junio C Hamano
2017-03-02 6:07 ` Johannes Sixt
2017-03-02 17:07 ` Junio C Hamano
2017-02-25 0:44 ` Linus Torvalds
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=xmqqbmublyo0.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=johannes.schindelin@gmx.de \
/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).