* Re: b4 dig struggling with some commits
2026-01-13 15:16 b4 dig struggling with some commits Mark Brown
@ 2026-01-13 15:15 ` Bugspray Bot
0 siblings, 0 replies; 2+ messages in thread
From: Bugspray Bot @ 2026-01-13 15:15 UTC (permalink / raw)
To: tools, bugs, broonie, konstantin
Hello:
This conversation is now tracked by Kernel.org Bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=220972
There is no need to do anything else, just keep talking.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
^ permalink raw reply [flat|nested] 2+ messages in thread
* b4 dig struggling with some commits
@ 2026-01-13 15:16 Mark Brown
2026-01-13 15:15 ` Bugspray Bot
0 siblings, 1 reply; 2+ messages in thread
From: Mark Brown @ 2026-01-13 15:16 UTC (permalink / raw)
To: Konstantin Ryabitsev; +Cc: tools
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
Hi Konstantin,
I've noticed that b4 dig -c frequently struggles with some commits, my
immediate example is -next commit
[2a0db5f7653b3576c430f8821654f365aaa7f178] struct filename: saner handling of long names
and I think most of the other examples are similar filesystem ones
(though that might just be that they're the ones I most often look at
that don't have a patch link in the commit log). I think the above
corresponds to:
https://lore.kernel.org/all/20260108073803.425343-16-viro@zeniv.linux.org.uk/
but ICBW.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-01-13 15:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-13 15:16 b4 dig struggling with some commits Mark Brown
2026-01-13 15:15 ` Bugspray Bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox