From: Marc Herbert <marc.herbert@linux.intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: Unreleased, multi-lines git_filter_repo fix required to run b4 tests?
Date: Fri, 31 Oct 2025 20:28:45 -0700 [thread overview]
Message-ID: <m2fray5t3m.fsf@C02X38VBJHD2mac.jf.intel.com> (raw)
In-Reply-To: <20251031-flashy-bouncy-macaw-2d5afa@lemur> (Konstantin Ryabitsev's message of "Fri, 31 Oct 2025 10:00:31 -0400")
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Thu, Oct 30, 2025 at 08:49:01PM -0700, Marc Herbert wrote:
>> So what really baffles me is: how come no one else noticed this before?
>
> They have -- it's a recurring problem for packagers.
Ha, then I was searching in the wrong place: here.
But wait... only packagers run tests? Not the people submitting b4
changes on this list!?
The "xfail" patch I just submitted should be enough to please packagers.
> I've been prodding git-filter-repo to release a fixed version -- if
> more people tell them about it, maybe this will actually happen?
Not sure what is a good stick there but for sure my xfail patch and the
corresponding effort should provide strong, additional evidence of how
painful this has been - whether you merge it or not. So... I've done my
share? :-)
> This bug doesn't really affect real usage of b4, because this only manifests
> itself when someone sets the cover letter strategy to use git branch
> descriptions (which is what tests do).
Good to know, thx.
prev parent reply other threads:[~2025-11-01 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 3:49 Unreleased, multi-lines git_filter_repo fix required to run b4 tests? Marc Herbert
2025-10-31 14:00 ` Konstantin Ryabitsev
2025-11-01 3:28 ` Marc Herbert [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=m2fray5t3m.fsf@C02X38VBJHD2mac.jf.intel.com \
--to=marc.herbert@linux.intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.