From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Cheap way to check for new messages in a thread
Date: Thu, 30 Mar 2023 12:45:07 -0400 [thread overview]
Message-ID: <20230330-service-handmade-0295eec6336f@meerkat> (raw)
In-Reply-To: <20230330112951.M493025@dcvr>
On Thu, Mar 30, 2023 at 11:29:51AM +0000, Eric Wong wrote:
> > Per-thread search is something I've wanted for a while, anyways,
> > so I think I'll do /$MSGID/?q= in between ongoing work for
>
> This implements the mbox.gz retrieval. I didn't want to deal
> with HTML nor figuring out how to expose more <form> elements,
> yet; but I figure mbox.gz is the most important.
Nice, thanks!
I can't easily test this, because lore is currently mostly on 1.9 and the
patch doesn't cleanly apply to that tree. However, I will be happy to test it
out once 2.0 is out and we've updated to it on our systems.
Cheers,
-K
next prev parent reply other threads:[~2023-03-30 16:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 15:08 Cheap way to check for new messages in a thread Konstantin Ryabitsev
2023-03-27 19:10 ` Eric Wong
2023-03-27 20:47 ` Konstantin Ryabitsev
2023-03-27 21:38 ` Eric Wong
2023-03-28 14:04 ` Konstantin Ryabitsev
2023-03-28 19:45 ` Eric Wong
2023-03-28 20:00 ` Konstantin Ryabitsev
2023-03-28 22:08 ` Eric Wong
2023-03-28 23:30 ` Konstantin Ryabitsev
2023-03-29 21:25 ` Eric Wong
2023-03-30 11:29 ` Eric Wong
2023-03-30 16:45 ` Konstantin Ryabitsev [this message]
2023-03-31 1:40 ` Eric Wong
2023-04-11 11:27 ` Eric Wong
2023-06-16 19:11 ` Konstantin Ryabitsev
2023-06-16 23:13 ` [PATCH] www: use correct threadid for per-thread search Eric Wong
2023-06-21 17:11 ` Konstantin Ryabitsev
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=20230330-service-handmade-0295eec6336f@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).