From: Eric Wong <e@yhbt.net>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: meta@public-inbox.org
Subject: Re: setting up mailman-to-atom-converter then atom-to-public-inbox
Date: Wed, 5 Feb 2020 00:10:02 +0000 [thread overview]
Message-ID: <20200205001002.GA5075@dcvr> (raw)
In-Reply-To: <CAPweEDy1qTK93pXDKdbT-HqJV184fH7x0hqqJYDTMv_nxvoKqQ@mail.gmail.com>
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Tuesday, February 4, 2020, Eric Wong <e@yhbt.net> wrote:
>
> >
> > Ah, right now mbox is only supported for one-off initial scripts
> > such as scripts/import_vger_from_mbox
> >
> > mbox is pretty bad for incremental updates, especially if
> > there's big rewrites going on for Status: flags setting off
> > inotify/EVFILT_VNODE.
>
> okaay sooOooo.... i am reconfigurink mailman to yoose maildir, ya?
Sure, or just have a subscriber (which can be yourself) set it up.
I do that with most of https://public-inbox.org/hosted.html
since I'm not an admin of any of those lists.
No admin intervention or even admin knowledge of the
public-inbox is even necessary. It's a bit subversive
like git-svn in that regard ;>
> will let you know how it goes.
Thanks!
next prev parent reply other threads:[~2020-02-05 0:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 18:42 setting up mailman-to-atom-converter then atom-to-public-inbox Luke Kenneth Casson Leighton
2020-02-04 20:55 ` Eric Wong
2020-02-04 21:49 ` Luke Kenneth Casson Leighton
2020-02-04 22:14 ` Eric Wong
[not found] ` <CAPweEDy1qTK93pXDKdbT-HqJV184fH7x0hqqJYDTMv_nxvoKqQ@mail.gmail.com>
2020-02-05 0:10 ` Eric Wong [this message]
[not found] ` <CAPweEDyYA+38B4uc+stMpZ9q6CrHaaAAkkorCuH4ONHmhBXbXg@mail.gmail.com>
2020-02-05 0:43 ` Eric Wong
2020-02-05 1:02 ` Kyle Meyer
2020-02-05 1:04 ` Eric Wong
2020-03-10 0:07 ` setting up mailman2 and public-inbox Luke Kenneth Casson Leighton
2020-03-11 10:33 ` Eric Wong
2020-03-11 11:58 ` Luke Kenneth Casson Leighton
2020-03-11 12:47 ` Luke Kenneth Casson Leighton
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=20200205001002.GA5075@dcvr \
--to=e@yhbt.net \
--cc=lkcl@lkcl.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).