From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: [PATCH] Don't coredump on bad refs in update-server-info.
Date: Wed, 31 Jan 2007 09:20:47 +0100 [thread overview]
Message-ID: <eppjeg$tgk$1@sea.gmane.org> (raw)
In-Reply-To: 20070131072444.GA28804@spearce.org
Shawn O. Pearce wrote:
> Apparently if we are unable to parse an object update-server-info
> coredumps, as it doesn't bother to check the return value of its
"Apparently if we are unable to parse an object _then_ update-server-info
coredumps" is a bit more easier to understand.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-01-31 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 7:24 [PATCH] Don't coredump on bad refs in update-server-info Shawn O. Pearce
2007-01-31 8:20 ` Jakub Narebski [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='eppjeg$tgk$1@sea.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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