From: Eric Wong <e@80x24.org>
To: Evan Gates <evan.gates@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] scripts: add script to export v1 inboxes to maildir
Date: Mon, 11 Apr 2022 20:36:47 +0000 [thread overview]
Message-ID: <20220411203647.M756942@dcvr> (raw)
In-Reply-To: <20220405230156.25449-1-evan.gates@gmail.com>
Evan Gates <evan.gates@gmail.com> wrote:
> ---
>
> I'm pretty sure this is a gross misuse of the public-inbox format, and
> as such will not be offended if you decide not to include this script.
Heh, OK :)
> I read the public-inbox README and liked the idea of the pull model.
> I briefly scanned clients.txt but didn't easily figure out how I was
> supposed to pull and read mail locally. Since the v1 format already
> has a bunch of uniquely named files, that are themselves emails,
> it was pretty simple to symlink them into a maildir format so I can
> read them in my mail client.
*gasp*
cloning v1 w/o bare gets really ugly for larger inboxes.
> As a followup to this abomination, what is the correct way to pull
> and read mail locally?
With v1.7.0+, the initial clone:
public-inbox-clone https://try.public-inbox.org/test public-inbox-test
public-inbox-index public-inbox-test
# search for all messages >0 bytes from the last year until now:
lei q -o /path/to/maildir -O public-inbox-test z:0.. rt:last.year..
# You can change "rt:last.year.." to any time range or leave it out,
# but giant Maildirs get too slow for me.
# periodic updates:
make -C public-inbox-test update
lei up /path/to/maildir
> +# cd ~/lists
> +# git clone https://public-inbox.org/meta public-inbox-meta
> +# git clone https://public-inbox.org/test public-inbox-test
"git clone" is fine for older versions, but --mirror (or --bare)
is strongly encouraged since v1 inboxes can grow trees w/o bounds.
prev parent reply other threads:[~2022-04-11 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 23:01 [PATCH] scripts: add script to export v1 inboxes to maildir Evan Gates
2022-04-11 20:36 ` Eric Wong [this message]
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=20220411203647.M756942@dcvr \
--to=e@80x24.org \
--cc=evan.gates@gmail.com \
--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).