git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2010, #03; Wed, 07)
Date: Thu, 08 Apr 2010 08:05:28 +0200	[thread overview]
Message-ID: <4BBD7228.8080403@viscovery.net> (raw)
In-Reply-To: <7v6342ahx9.fsf@alter.siamese.dyndns.org>

Am 4/8/2010 2:48, schrieb Junio C Hamano:
> * np/malloc-threading (2010-04-07) 2 commits
>  - Make xmalloc and xrealloc thread-safe (addendum)
>  - Make xmalloc and xrealloc thread-safe
> 
> Updated with Freku's "init_recursive_mutex()".  The fix should eventually
> go to 'maint' and 'master'.

The addendum does not compile on Windows. I'm working on a replacement.

BTW, are there Unices that do not have a recursive mutex?

-- Hannes

  reply	other threads:[~2010-04-08  6:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  0:48 What's cooking in git.git (Apr 2010, #03; Wed, 07) Junio C Hamano
2010-04-08  6:05 ` Johannes Sixt [this message]
2010-04-08  6:33   ` Junio C Hamano
2010-04-08  9:01     ` Fredrik Kuivinen
2010-04-08  9:14       ` ***SPAM*** " Tor Arntsen
2010-04-08  9:16         ` Tor Arntsen
2010-04-08  7:38 ` Jeff King
2010-04-08 21:42   ` nd/setup Jonathan Nieder
2010-04-09  0:13     ` nd/setup Jeff King
2010-04-11 11:01       ` [PATCH] Take it easy on unallowed access to non-existent repository Nguyễn Thái Ngọc Duy
2010-04-11 15:45         ` Sverre Rabbelier
2010-04-11 17:49           ` Nguyen Thai Ngoc Duy
2010-04-11 17:52             ` Sverre Rabbelier
2010-04-11 17:57               ` Nguyen Thai Ngoc Duy
2010-04-09  5:46     ` nd/setup Nguyen Thai Ngoc Duy
2010-04-09  5:57       ` nd/setup Jonathan Nieder
2010-04-09  6:56         ` nd/setup Nguyen Thai Ngoc Duy
2010-04-11 17:57     ` nd/setup Nguyen Thai Ngoc Duy

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=4BBD7228.8080403@viscovery.net \
    --to=j.sixt@viscovery.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.
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 NNTP newsgroup(s).