From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Philipp Hahn" <phahn-oss@avm•de>, git@vger•kernel.org
Subject: Re: BUG: commit-graph + objects/alternate -> SIGSEGV
Date: Fri, 17 Oct 2025 11:54:32 +0200 [thread overview]
Message-ID: <68e5557c-3981-4378-bc76-2a986567a699@app.fastmail.com> (raw)
In-Reply-To: <20251017094717.626300-1-phahn-oss@avm.de>
On Fri, Oct 17, 2025, at 11:47, Philipp Hahn wrote:
>[snip]
> What happened instead? (Actual behavior)
>
> `git fetch` crashes with a SIGSEGV respective complains about "missing
> commit-graphs":
> > Warnung: konnte nicht alle Commit-Graph-Dateien finden
The English translation for that on Git 2.43.0 is
unable to find all commit-graph files
prev parent reply other threads:[~2025-10-17 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 9:47 BUG: commit-graph + objects/alternate -> SIGSEGV Philipp Hahn
2025-10-17 9:54 ` Kristoffer Haugsbakk [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=68e5557c-3981-4378-bc76-2a986567a699@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=phahn-oss@avm$(echo .)de \
/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