From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Tal Zussman <tz2294@columbia.edu>
Cc: tools@kernel.org
Subject: Re: b4 broken with git older than 2.41
Date: Wed, 28 May 2025 14:27:14 -0400 [thread overview]
Message-ID: <20250528-active-pumpkin-tapir-3e912d@lemur> (raw)
In-Reply-To: <CAKha_sri+u=R9x1h9tg7N4cuTFckLmbe22=Sw2P2jpw_fm2Jcg@mail.gmail.com>
On Wed, May 28, 2025 at 02:15:16AM -0400, Tal Zussman wrote:
> Hi,
>
> I am using b4 (both master and 0.14.y) on Debian 12 with git 2.39.5
> (the latest available).
> Unfortunately, it is failing with errors such as:
> "CRITICAL: Failed to convert range to patches: Could not get a patch
> out of bfd12f86c8a48927959a7d88c84296823e15a8f9."
>
> I narrowed this down to the use of the '--default-prefix' option in
> git_range_to_patches(), which seems to have been added in git v2.41.
> Once I commented that out, everything worked fine.
> Is there a minimum supported git version listed somewhere?
Hm... we should make things work with that version of git. I wasn't aware of
this limitation.
Thanks for the report.
bugspray tag me
-K
next prev parent reply other threads:[~2025-05-28 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 6:15 b4 broken with git older than 2.41 Tal Zussman
2025-05-28 18:27 ` Konstantin Ryabitsev [this message]
2025-05-28 18:30 ` Bugspray Bot
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=20250528-active-pumpkin-tapir-3e912d@lemur \
--to=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=tz2294@columbia.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).