From: Nicolas Pitre <nico@fluxnic.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2010, #01; Fri, 02)
Date: Sat, 03 Apr 2010 00:58:14 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1004030055110.694@xanadu.home> (raw)
In-Reply-To: <7vaatmckmi.fsf@alter.siamese.dyndns.org>
On Fri, 2 Apr 2010, Junio C Hamano wrote:
> * np/malloc-threading (2010-03-24) 1 commit
> - Make xmalloc and xrealloc thread-safe
>
> Still has locking issues?
Indeed.
Nicolas
prev parent reply other threads:[~2010-04-03 4:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 8:40 What's cooking in git.git (Apr 2010, #01; Fri, 02) Junio C Hamano
2010-04-02 11:23 ` Nguyen Thai Ngoc Duy
2010-04-03 5:00 ` nd/setup Jonathan Nieder
2010-04-03 14:39 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-04 18:41 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-04 21:42 ` nd/setup Junio C Hamano
2010-04-02 16:48 ` What's cooking in git.git (Apr 2010, #01; Fri, 02) Sverre Rabbelier
2010-04-03 4:58 ` Nicolas Pitre [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=alpine.LFD.2.00.1004030055110.694@xanadu.home \
--to=nico@fluxnic.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).