Re: [b4] initial "b4 dig" to supplant Link: trailers

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Tue, Oct 14, 2025 at 05:49:31PM -0400, Sasha Levin wrote:
> 1. If the provided commit actually has a Link: trailer, we should just use
> that(?).

We do, but we now do it better in the latest master.

> 2. Some maintainers re-send patches they've accepted. An example:
> 
> $ ~/b4/b4.sh dig -c 54b91e54b113d4f15ab023a44f508251db6e22e7 Digging into
> commit 54b91e54b113d4f15ab023a44f508251db6e22e7
> Attempting to match by exact patch-id...
> Trying to find matching series by patch-id 340e7baae92a71dd5e62a4e8a52245348ff3a0a1 (myers)
> Found matching series by patch-id
> Will consider promising messages: 2
> ---
> [for-linus][PATCH v2 2/2] tracing: Stop fortify-string from warning in tracing_mark_raw_write()
> https://lore.kernel.org/r/20251011194257.341582199@kernel.org
> 
> Which doesn't end up pointing to the actual submission. I'm not really sure
> whats the "correct" way of addressing this...

There isn't a good way to deal with this. In this particular case there's a
Link: trailer in the commit, so we can filter by that to find the right patch,
but failing that it's a pattern that will always "win" because it's newer and
from the same author.

> 3. Date filtering seems to be broken:

Rather, I found that using rt: is not always effective for some reason, so I
switched to using d:, which seems to be more reliable.

-K