All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2020, #02; Mon, 10)
Date: Tue, 11 Aug 2020 12:20:48 -0700	[thread overview]
Message-ID: <xmqqbljh9egf.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAHd-oW7Wd8oSaMhPFeRcEeKTJ-k_hC7b6e28efhXT5LFu1E_Uw@mail.gmail.com> (Matheus Tavares Bernardino's message of "Tue, 11 Aug 2020 11:27:04 -0300")

Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:

> Hi, Junio
>
> On Mon, Aug 10, 2020 at 4:44 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * mt/hash-to-hex-thread-safety (2020-06-26) 2 commits
>>  - hex: make hash_to_hex_algop() and friends thread-safe
>>  - compat/win32/pthread: add pthread_once()
>>
>>  hash_to_hex() used a set of rotating static buffers, which was not
>>  safe to use in a threaded environment.  This has been made safer by
>>  using thread-local storage.
>>
>>  Expecting a reroll.
>>  cf. <CAHd-oW6A2aBHg80R9kyifvF7thwzam5EYYoN9d2TaBcHJrcKWw@mail.gmail.com>
>
> I think we can drop this one.

OK.  Thanks.

      reply	other threads:[~2020-08-11 19:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 19:44 What's cooking in git.git (Aug 2020, #02; Mon, 10) Junio C Hamano
2020-08-11  5:01 ` Eric Sunshine
2020-08-11 19:24   ` Junio C Hamano
2020-08-11  6:53 ` Jeff King
2020-08-11  9:33   ` Patrick Steinhardt
2020-08-11  9:59   ` brian m. carlson
2020-08-11 10:10 ` Sergey Organov
2020-08-11 19:23   ` Junio C Hamano
2020-08-11 19:34     ` Sergey Organov
2020-08-11 20:17       ` Sergey Organov
2020-08-11 21:36         ` Junio C Hamano
2020-08-12  8:15           ` Sergey Organov
2020-08-11 20:28       ` Junio C Hamano
2020-08-11 21:26         ` Sergey Organov
2020-08-11 22:12           ` Junio C Hamano
2020-08-11 13:48 ` Taylor Blau
2020-08-11 14:27 ` Matheus Tavares Bernardino
2020-08-11 19:20   ` Junio C Hamano [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqbljh9egf.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    /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.