can patchew search be switched to not insist on exact full-word matches?

[pm215]

It would be nice if patchew was less strict about only searching for exact word matches. For instance, you can only find this patch:
https://patchew.org/QEMU/20200610084551.28222-1-vav@sysgo.com/
("hw/timer/a9gtimer: Clear pending interrupt, after the clear of Event flag")
if you search for "hw/timer/a9gtimer", because it does not match a search for "a9gtimer". (As a comparison, the "patches" command line tool doesn't do word-matches, so this patch can be found by searching for "a9gtimer" or even just "gtimer".)

[bonzini]

Matching on full words gives is by design, but splitting on slashes is definitely a good idea. We use postgres full text search so I have to figure out how to configure it (or perhaps just replace non-ascii characters with spaces before indexing).

[bonzini]

I tried doing this on next.patchew.org, but the most straightforward way in postgres seems to be to have another field with the searchable content. updating the database to create it took too much time (i halted it after a couple minutes) even if it is in theory just a few thousand rows.

I may revisit it later.