From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Michael Haggerty <mhagger@alum.mit.edu>
Subject: [PATCH 0/2] refs/files-backend: fix two subtle error-handling bugs
Date: Thu, 21 Mar 2019 05:28:29 -0400 [thread overview]
Message-ID: <20190321092829.GA2648@sigill.intra.peff.net> (raw)
This series fixes two bugs around the error-handling of writing
packed-refs during ref deletion. The first one came from a real-world
case. The second is impossible to trigger (currently), but since I
noticed it while hunting the first one, I figured it was worth fixing.
[1/2]: refs/files-backend: handle packed transaction prepare failure
[2/2]: refs/files-backend: don't look at an aborted transaction
refs/files-backend.c | 16 +++++++++++++++-
t/t1404-update-ref-errors.sh | 16 ++++++++++++++++
2 files changed, 31 insertions(+), 1 deletion(-)
-Peff
next reply other threads:[~2019-03-21 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 9:28 Jeff King [this message]
2019-03-21 9:28 ` [PATCH 1/2] refs/files-backend: handle packed transaction prepare failure Jeff King
2019-03-22 0:06 ` Jeff King
2019-03-22 14:34 ` Taylor Blau
2019-03-21 9:28 ` [PATCH 2/2] refs/files-backend: don't look at an aborted transaction 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190321092829.GA2648@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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).