tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@kernel.org, tools@kernel.org
Subject: Re: [b4] initial "b4 dig" to supplant Link: trailers
Date: Tue, 14 Oct 2025 22:52:42 -0400	[thread overview]
Message-ID: <yq1347kc3bu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251014-gorgeous-cougar-of-endeavor-0c5baa@lemur> (Konstantin Ryabitsev's message of "Tue, 14 Oct 2025 17:17:43 -0400")


Hi Konstantin!

> "b4 dig -c [commitish] --all-series" will now try to find all the
> series where that patch belongs and try to get you links to all prior
> revisions, even if they don't have that very patch (e.g. because it
> only appeared in v3).

There is some funky stuff going on with the date range limit. b4 dig
currently misses some messages for which the patch-id can be queried on
lore:

    ecode, out = b4.git_run_command(
        topdir, ['show', '--no-patch', '--format=%as %ae %s', commit],
    )

The resulting %as cdate will be in the format "2025-10-07". However,
specifying a query date limit of "rt:..2025-10-07" means the patch mail
will be missed:

    Full query: patchid:3c67a3033590c511bc96819aa2fdc6376c2799e1 AND rt:..2025-10-07 (nocache=False)
    Grabbing search results from lore.kernel.org
    Nothing matching that query.

Whereas my own script finds it:

    $ check-lore 3c67a3033590c511bc96819aa2fdc6376c2799e1
    Found 3c67a3033590c511bc96819aa2fdc6376c2799e1 on lore.kernel.org

Bumping the cdate to 2025-10-08 makes b4 dig find the message.

I don't know anything about Xapian and how it indexes. But I assume
there might be some fun with time zones and DST lurking here...

-- 
Martin K. Petersen

  parent reply	other threads:[~2025-10-15  2:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 20:47 [b4] initial "b4 dig" to supplant Link: trailers Konstantin Ryabitsev
2025-10-11 12:39 ` Greg KH
2025-10-13  8:13   ` Peter Zijlstra
2025-10-11 20:08 ` Geert Uytterhoeven
2025-10-11 22:46 ` Linus Torvalds
2025-10-11 23:38   ` Sasha Levin
2025-10-11 23:44     ` Linus Torvalds
2025-10-12  0:39       ` Sasha Levin
2025-10-12 23:17       ` Jason Gunthorpe
2025-10-13 17:12 ` Mark Brown
2025-10-13 17:36   ` Linus Torvalds
2025-10-14 21:17 ` Konstantin Ryabitsev
2025-10-14 21:49   ` Sasha Levin
2025-10-15 13:47     ` Konstantin Ryabitsev
2025-10-14 22:13   ` Mark Brown
2025-10-15 13:44     ` Konstantin Ryabitsev
2025-10-15 13:52       ` Mark Brown
2025-10-15 16:40       ` Rob Herring
2025-10-15  2:52   ` Martin K. Petersen [this message]
2025-10-15 13:43     ` Konstantin Ryabitsev
2025-10-15 17:37       ` Martin K. Petersen

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=yq1347kc3bu.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@kernel.org \
    --cc=users@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 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).