From: Eli Zaretskii <eliz@gnu.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: eric@ericabrahamsen.net, emacs-devel@gnu.org
Subject: Re: How to search on emacs-devel?
Date: Thu, 10 Mar 2022 08:51:00 +0200 [thread overview]
Message-ID: <83ee3ae1wr.fsf@gnu.org> (raw)
In-Reply-To: <87wnh22w7o.fsf@kyleam.com> (message from Kyle Meyer on Thu, 10 Mar 2022 00:49:31 -0500)
> From: Kyle Meyer <kyle@kyleam.com>
> Date: Thu, 10 Mar 2022 00:49:31 -0500
> Cc: emacs-devel@gnu.org
>
> Eric Abrahamsen writes:
>
> > Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> >
> >> Andreas Schwab <schwab@linux-m68k.org> writes:
> >>
> >>> public-inbox is git under the hood (see
> >>> https://yhetil.org/emacs-devel/_/text/mirror/).
> >>
> >> Maybe local indexing with notmuch or what have you is still the easiest
> >> solution, to.
>
> For those that want to go this route, the main thing is getting the
> Git-stored messages [1] into a format that the indexer understands.
> There are some existing tools (not part of public-inbox) that can
> convert a public-inbox archive into a Maildir. l2md [2] and impibe [3]
> are the ones listed at
> <https://public-inbox.org/public-inbox.git/plain/Documentation/clients.txt>,
> though I haven't used either of them myself. (There's also
> public-inbox's lei, which I'll get to below.)
Instead (or maybe in addition to) of working on solutions that will
help people individually and locally, why not talk to the GNU mailman
admins so that this issue could be solved as part of improving the
search facilities of the mailman archives? That would benefit all of
us. Not to mention that "heavy" solutions are much more likely to be
deployed as part of the GNU mailman infrastructure than by individual
users on their local machines.
Thanks.
next prev parent reply other threads:[~2022-03-10 6:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 18:51 How to search on emacs-devel? Eric Abrahamsen
2022-03-09 18:59 ` Eric Abrahamsen
2022-03-09 19:24 ` Stefan Monnier
2022-03-09 19:49 ` Eric Abrahamsen
2022-03-09 21:46 ` Stefan Monnier
2022-03-09 22:01 ` Eric Abrahamsen
2022-03-09 22:12 ` Stefan Monnier
2022-03-09 22:23 ` Eric Abrahamsen
2022-03-10 5:49 ` Kyle Meyer
2022-03-10 6:51 ` Eli Zaretskii [this message]
2022-03-10 17:43 ` Eric Abrahamsen
2022-03-10 17:56 ` Eli Zaretskii
2022-03-10 18:12 ` Eric Abrahamsen
2022-03-10 17:54 ` Eric Abrahamsen
-- strict thread matches above, loose matches on Subject: below --
2022-03-08 15:09 dalanicolai
2022-03-08 15:17 ` dalanicolai
2022-03-08 15:57 ` andrés ramírez
2022-03-08 16:06 ` dalanicolai
2022-03-08 17:49 ` Philip Kaludercic
2022-03-08 18:13 ` Eric Abrahamsen
2022-03-09 13:34 ` Robert Pluim
2022-03-09 15:44 ` Eric Abrahamsen
2022-03-09 17:36 ` Stefan Monnier
2022-03-09 17:43 ` Andreas Schwab
2022-03-10 15:50 ` Felix Dietrich
2022-03-10 16:46 ` Felix Dietrich
2022-03-09 11:41 ` dalanicolai
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ee3ae1wr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=kyle@kyleam.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).