From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: inbox.sourceware.org experiment
Date: Tue, 16 Aug 2022 18:10:58 -0400 [thread overview]
Message-ID: <YvwV8nmPT8LFkx4X@elastic.org> (raw)
In-Reply-To: <YvwN0QZbKA+N9hN8@wildebeest.org>
Hi -
> It turns out public-inbox does support importing a full mbox in one
> go. But it doesn't have a nice binary for it yet. There is however
> scripts/import_vger_from_mbox in upstream git which is easily adapted
> (just remove the vger specific filtering).
This is already 99% done for the sourceware mailing lists.
> [...]
> Note this is V2 plus full indexing and includes and extra historical
> elfutils-devel.nospam.mbox
Is there a need for "full" indexing as opposed to "basic"? I don't
see why we'd need another text search engine for this stuff, we
already have. The basic "v1" with basic indexing seems fine and
effective for web and nntp.
> [...]
> I don't have a solution for keeping the archive up to date. [...]
We can hack a postfix->|mailman and |inbox-mda alias-fork
and dual pipe delivery for each mailing list.
- FChE
next prev parent reply other threads:[~2022-08-16 22:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 14:14 Mark Wielaard
2022-08-15 13:00 ` Mark Wielaard
2022-08-16 21:36 ` Mark Wielaard
2022-08-16 22:10 ` Frank Ch. Eigler [this message]
2022-08-17 12:25 ` Mark Wielaard
2022-08-17 13:24 ` Frank Ch. Eigler
2022-08-17 21:18 ` Mark Wielaard
2022-08-17 21:33 ` Frank Ch. Eigler
2022-08-18 13:50 ` Mark Wielaard
2022-08-18 14:40 ` Simon Marchi
2022-08-21 17:41 ` Mark Wielaard
2022-08-23 20:15 ` Mark Wielaard
2022-08-23 22:08 ` Mark Wielaard
2022-08-24 10:05 ` Mark Wielaard
2022-08-24 21:06 ` Mark Wielaard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvwV8nmPT8LFkx4X@elastic.org \
--to=fche@elastic.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).