From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/6] fix some parse_commit segfaults
Date: Thu, 24 Oct 2013 04:52:14 -0400 [thread overview]
Message-ID: <20131024085213.GA1267@sigill.intra.peff.net> (raw)
This is a repost of the series here:
http://thread.gmane.org/gmane.comp.version-control.git/235735/focus=235826
(the original was a single patch, followed by a 5-patch series, which
I've combined here). It's mostly a cleanup, since parse_commit will only
fail in corrupted repos, but I did run into it in a real (corrupted)
repo.
[1/6]: log_tree_diff: die when we fail to parse a commit
[2/6]: assume parse_commit checks commit->object.parsed
[3/6]: assume parse_commit checks for NULL commit
[4/6]: use parse_commit_or_die instead of segfaulting
[5/6]: use parse_commit_or_die instead of custom message
[6/6]: checkout: do not die when leaving broken detached HEAD
-Peff
next reply other threads:[~2013-10-24 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 8:52 Jeff King [this message]
2013-10-24 8:52 ` [PATCH 1/6] log_tree_diff: die when we fail to parse a commit Jeff King
2013-10-24 8:53 ` [PATCH 2/6] assume parse_commit checks commit->object.parsed Jeff King
2013-10-24 8:53 ` [PATCH 3/6] assume parse_commit checks for NULL commit Jeff King
2013-10-24 8:53 ` [PATCH 4/6] use parse_commit_or_die instead of segfaulting Jeff King
2013-10-24 8:54 ` [PATCH 5/6] use parse_commit_or_die instead of custom message Jeff King
2013-10-24 8:54 ` [PATCH 6/6] checkout: do not die when leaving broken detached HEAD Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131024085213.GA1267@sigill.intra.peff.net \
--to=peff@peff.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).