09:14 pq: Did I understand correctly that some (DRM) maintainers are using a web service (lore.kernel.org) for reading email, because using an actual email client is just too painful and an actual inbox might overflow? Or are they using some non-browser interface to lore?
09:17 emersion: it depends
09:17 emersion: i think lore is mostly used for linking to discussions
09:17 emersion: i believe most folks still receive all mail
09:19 pq: lore seemed to have nice filtering rules available
09:24 emersion: yeah, i'd like to try to use that
09:25 pq: how would one reply to emails found via lore, though?
09:26 phasta: I search for relevant components in my dri-devel inbox and lore at times in case someone forgot to CC me
09:29 MTCoster: You can download the message/thread from lore and load it into your mail client
09:29 pq: MTCoster, with some mail client specific scripting I suppose?
09:29 llyyr: you just need to set the In-Reply-To header, thunderbird lets you do it though it's a bit hidden
09:30 MTCoster: I do it so rarely I just download the mbox from lore and import it into thunderbird using the ImportExportToolsNG extension
09:30 pq: llyyr, that sounds quite manual, and would also need to manually copy the original content.
09:31 llyyr: yeah, that's what I do when I need to reply to mails I didn't receive for whatever reason. I don't know if there's a good automated solution
09:32 pq: I wonder how sima does it, my wondering started from her comments like getting cc'd so much that cc has no value anymore.
09:32 emersion: i also occasionally import mbox files
09:32 sima: pq, lore comes with lei, which is a local cli tool to dump your lore searches into local Mailboxes
09:33 emersion: (i thought vanilla thunderbird supported mbox import?)
09:33 sima: which you can then read and use for replies with any mua
09:33 emersion: (i don't know, i don't use thunderbird)
09:33 sima: plus for lists I don't subscribe I just grab the mbox from lore as needed
09:33 pq: I think it would be nice if I could simply stop archiving (badly) a copy of the dri-devel list.
09:33 pq: sima, ooh, lei, I've heard of it, but totally forgot.
09:35 MTCoster: emersion: It might, I started using IETng because it lets you deal with directories of .eml files too
09:37 MrCooper: TB can load a single e-mail from a file, can't seem to handle an mbox file with multiple messages properly though
09:38 emersion: that's unfortunate
09:40 pq: I even had https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started bookmarked >_<
13:51 austriancoder: I’m asking while already knowing the answer: Adding a new EGL extension to Mesa requires it to be listed in the KhronosGroup EGL Registry. Is that correct?
14:02 austriancoder: daniels: ^ maybe you can answer that?
14:07 daniels: austriancoder: yep
14:15 austriancoder: thx
15:29 dcbaker: eric_engestrom: If I could get your help, the release from last week is way behind, but I'm home sick with sick kiddos. I set a job to merge the staging branch into the 24.3 branch, but I haven't run the scripts to make the release, would it be possible for you to do that for me?
15:58 cmarcelo: is there a way to search for "something OR otherthing" (trying to match two different words in title of the issues) in the GitLab issues?
15:59 cmarcelo: documentation I've found points to a premium version, and the gitlab edit field popup helps aren't helpful.
21:00 mareko: zmike: what can we do to merge this? https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32789
21:30 zmike: mareko: uhhh that's a good q
21:30 zmike: I'll dig in a bit deeper tomorrow during khronos calls
21:34 zmike: as I've said on the MR it's probably not a faulty job since every single system I have experiences this issue across every driver
21:34 zmike: including yours