git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Cc: ArcticLampyrid <ArcticLampyrid@outlook.com>,
	Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: [PATCH 0/2] bundle: fix handling of object format
Date: Tue, 13 Aug 2024 11:18:05 +0200	[thread overview]
Message-ID: <cover.1723540604.git.ps@pks.im> (raw)
In-Reply-To: <TYWP301MB0563973ECA440E7DAF0F7E89C4852@TYWP301MB0563.JPNP301.PROD.OUTLOOK.COM>

Hi,

this small patch series addresses the segfaults reported by
ArcticLampyrid and fixes parsing of bundles that have an object hash
different than the object hash of the current repository.

Thanks!

Patrick

Patrick Steinhardt (2):
  builtin/bundle: have unbundle check for repo before opening its bundle
  bundle: default to SHA1 when reading bundle headers

 builtin/bundle.c       |  5 +++--
 bundle.c               |  7 ++++++-
 t/t6020-bundle-misc.sh | 32 ++++++++++++++++++++++++++++++++
 3 files changed, 41 insertions(+), 3 deletions(-)

-- 
2.46.0.46.g406f326d27.dirty


  parent reply	other threads:[~2024-08-13  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 10:57 SIGSEGV Error Occurs When Attempting to Unbundle Without Initializing Git Repository ArcticLampyrid
2024-08-12 11:47 ` Jeff King
2024-08-12 15:55   ` Junio C Hamano
2024-08-12 21:05   ` brian m. carlson
2024-08-13  9:18 ` Patrick Steinhardt [this message]
2024-08-13  9:18   ` [PATCH 1/2] builtin/bundle: have unbundle check for repo before opening its bundle Patrick Steinhardt
2024-08-13  9:21     ` Eric Sunshine
2024-08-13  9:18   ` [PATCH 2/2] bundle: default to SHA1 when reading bundle headers Patrick Steinhardt
2024-08-13 11:24     ` Jeff King
2024-08-13 15:11       ` Junio C Hamano

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=cover.1723540604.git.ps@pks.im \
    --to=ps@pks.im \
    --cc=ArcticLampyrid@outlook.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=sandals@crustytoothpaste.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 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).