From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: yes [Re: should lei attempt to index mail outside of git?]
Date: Sun, 2 May 2021 06:12:11 +0000 [thread overview]
Message-ID: <20210502061211.GA12765@dcvr> (raw)
In-Reply-To: <20210303035359.GA14438@dcvr>
Eric Wong <e@80x24.org> wrote:
> Currently, every mail lei indexes has a git blob associated with it.
It still will. But we have PublicInbox::ContentHash::git_sha
> I understand some folks might want to keep using their existing
> storage and not have a redundant, expensive-to-erase copy of the
> mail in git; but just want an indexing-only solution like mairix.
At least for Maildir, IMAP, and NNTP where random access is
reliable and fast, it should be doable.
> So, is this a feature worth implementing?
Since we have ~/.local/share/lei/store/mail_sync.sqlite3
nowadays, I think it's possible to make LeiToMail fallback
to retrieving from Maildir, IMAP, NNTP; at least. mbox
can be a pain since message offsets can change.
prev parent reply other threads:[~2021-05-02 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 3:53 should lei attempt to index mail outside of git? Eric Wong
2021-05-02 6:12 ` 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=20210502061211.GA12765@dcvr \
--to=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).