All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jim Meyering <jim@meyering.net>
Cc: git list <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] avoid NULL dereference on failed malloc
Date: Mon, 15 Jun 2009 09:49:15 +0200	[thread overview]
Message-ID: <4A35FCFB.1080000@drmicha.warpmail.net> (raw)
In-Reply-To: <87hbyioayl.fsf@meyering.net>

Jim Meyering venit, vidit, dixit 14.06.2009 21:46:
> 
> * builtin-remote.c (get_one_entry): Use xmalloc, not malloc.

Learning something new with every patch... Sorry, Junio; thanks, Jim!

Michael

  reply	other threads:[~2009-06-15  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 19:46 [PATCH] avoid NULL dereference on failed malloc Jim Meyering
2009-06-15  7:49 ` Michael J Gruber [this message]
2009-06-15 20:45   ` [PATCH] builtin-remote: (get_one_entry): use strbuf Bert Wesarg
2009-06-16  7:39     ` Michael J Gruber
2009-06-16  7:56       ` Bert Wesarg
2009-06-16 10:49         ` Michael J Gruber
2009-06-22  8:24           ` Bert Wesarg
2009-06-22 21:32             ` Jeff King
2009-06-22 22:27               ` [PATCH v2] " Bert Wesarg

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=4A35FCFB.1080000@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jim@meyering.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.