From: Eric Wong <email@example.com> To: Rob Herring <firstname.lastname@example.org> Cc: Konstantin Ryabitsev <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH] searchidx: index "diff --git a/... b/..." headers Date: Tue, 9 Nov 2021 05:08:27 +0000 [thread overview] Message-ID: <20211109050827.GA28454@dcvr> (raw) In-Reply-To: <CAL_Jsq+Eqru9qGwU3QKVVbdN5o7md-0YcZHVkBB-egDD0email@example.com> Rob Herring <firstname.lastname@example.org> wrote: > On Mon, Nov 8, 2021 at 9:12 PM Eric Wong <email@example.com> wrote: > > I think 's:patch' should be sufficient, don't think there's > > many false-positives on that front, actually. > > It's at least 's:patch OR s:rfc OR s:resend'. That catches all but the > few creative folks that come up with something else. > > > With this fix, nq:"diff --git" should also be working across > > https://yhbt.net/lore/ in about 40 hours (whenever reindex > > finishes) > > 'diff --git' should cover probably 99.9% of patches but there are > still some non-git diffs from time to time. OK, so maybe the combination of: s:patch OR s:rfc OR s:resend OR nq:"diff --git" Is enough? Maybe it would be good do support some form of alias expansion in the Xapian query parser for "common" things like that. I know there's a few not-seriously-proposed patches which may lack all of those, but perhaps they weren't meant to be applied, either... Fwiw, it would also be useful to have it expand .mailmap and sendemail.aliasesfile entries, too. Unfortunately, I think doing aliases cleanly requires dropping down to C++ to supply custom routines to Xapian. The current approxidate parsing is all done via fragile string substitutions; I'm not sure how that holds up... > > I'm not sure if there needs to be a specific term to index > > patches on; maybe there is. There's still a lot of Xapian > > we're not using, yet... > > What I'm hoping to get to is a replacement for patchwork in my > workflow. For that I want all patches which don't have either a > Reviewed/Acked tag from me or a reply from me. I think the first part > should be possible with lei, but I'd imagine the last part is some > processing on top of the lei query. Yes, exactly. Powerful-enough local search should be able to replace many web-based tools. Patch indexing could take into account git trailers, but maybe existing 'nq:' phrases are enough *shrug* lei is still primitive, but things like "lei p2q" can be combined to do some patch tracking. An example from the lei-p2q(1) manpage: # to view unapplied patches for a given $FILE from the past year: echo \( rt:last.year.. AND dfn:$FILE \) AND NOT \( \ $(git log -p --pretty=mboxrd --since=last.year $FILE | lei p2q -F mboxrd ) \) | lei q -o /tmp/unapplied I do need some time to consider future features and non-bugfix stuff to lei+public-inbox, though. There's already a huge amount of stuff in the TODO and a billion things in my life that also need fixing :<
prev parent reply other threads:[~2021-11-09 5:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> [not found] ` <CAL_JsqJBh1O3H2-P07AHzVq0x89BoP_N6P=rT5up6=3QyF_B0Q@mail.gmail.com> 2021-11-08 20:22 ` lei: incorrect quoting on saved searches (was Re: lore+lei: getting started) Konstantin Ryabitsev 2021-11-08 20:49 ` Eric Wong 2021-11-08 21:36 ` Konstantin Ryabitsev 2021-11-08 21:48 ` Eric Wong 2021-11-08 22:36 ` Konstantin Ryabitsev 2021-11-08 22:57 ` Eric Wong 2021-11-08 20:53 ` Rob Herring 2021-11-08 21:27 ` [PATCH] searchidx: index "diff --git a/... b/..." headers Eric Wong 2021-11-09 0:38 ` Rob Herring 2021-11-09 3:12 ` Eric Wong 2021-11-09 4:03 ` Rob Herring 2021-11-09 5:08 ` Eric Wong [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 List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20211109050827.GA28454@dcvr \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] searchidx: index "diff --git a/... b/..." headers' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/public-inbox.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).