From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff King <peff@peff.net>,
git@vger.kernel.org, Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: [PATCH] mingw: use OpenSSL's SHA-1 routines
Date: Thu, 2 Mar 2017 07:07:22 +0100 [thread overview]
Message-ID: <fa38e22e-3114-fab8-38ed-5f52125e81bb@kdbg.org> (raw)
In-Reply-To: <xmqqmvdbz23d.fsf@gitster.mtv.corp.google.com>
Am 24.02.2017 um 22:54 schrieb Junio C Hamano:
> Johannes Sixt <j6t@kdbg.org> writes:
>> I'll use the patch for daily work for a while to see whether it hurts.
>
> Please ping this thread again when you have something to add. For
> now, I'll demote this patch from 'next' to 'pu' when we rewind and
> rebuild 'next' post 2.12 release.
As I already said in [1], I have no objection. I've used the patch in
production for some time now and did not notice any slowdowns.
[1]
https://public-inbox.org/git/0080edd6-a515-2fe9-6266-b6f6bbedfdde@kdbg.org/
-- Hannes
next prev parent reply other threads:[~2017-03-02 6:10 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa38e22e-3114-fab8-38ed-5f52125e81bb@kdbg.org \
--to=j6t@kdbg.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=peff@peff.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.