From: Junio C Hamano <junkio@cox.net>
To: Carl Worth <cworth@cworth.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Prevent git-upload-pack segfault if object cannot be found
Date: Fri, 17 Feb 2006 22:50:17 -0800 [thread overview]
Message-ID: <7vd5hlupna.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 87hd6x34lf.wl%cworth@cworth.org
Thanks, this is the last remaining call that did not check its
return value from opendir().
I queued this one and three clone things from you. They will
appear in "next" first, but also be in 1.2.2.
next prev parent reply other threads:[~2006-02-18 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 0:14 [PATCH] Prevent git-upload-pack segfault if object cannot be found Carl Worth
2006-02-18 6:50 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 18:17 Andrew Vasquez
2006-02-22 18:26 ` Junio C Hamano
2006-02-22 18:44 ` Carl Worth
2006-02-22 18:50 ` Junio C Hamano
2006-02-22 19:11 ` Junio C Hamano
2006-02-22 19:16 ` Carl Worth
2006-02-23 0:34 ` Jonas Fonseca
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=7vd5hlupna.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
/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).