user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Danh Doan <congdanhqx@gmail.com>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: How to Extract public-inbox v2 to Maildir
Date: Sun, 26 Apr 2020 21:19:23 +0700	[thread overview]
Message-ID: <20200426141923.GC14800@danh.dev> (raw)
In-Reply-To: <20200426060542.GA15896@dcvr>

On 2020-04-26 06:05:42+0000, Eric Wong <e@yhbt.net> wrote:
> Danh Doan <congdanhqx@gmail.com> wrote:
> > To my surprise, it doesn't work because lore.kernel.org use version
> > 2 of public-inbox's repository.
> 
> Right...
> 
> > Would it is easy (and desired) to have this in public-inbox, since
> > I saw a notice that ssoma won't support v2.
> 
> If you like Maildir, there's l2md:
> https://git.kernel.org/pub/scm/linux/kernel/git/dborkman/l2md.git/
> 
> I guess it'd be helpful to have a clients list in our
> documentation somewhere...
> 
> Maybe I'll have time to work on some client tools, probably in
> the vein of mairix where it'll dump search results into a
> Maildir/mbox/IMAP folder.
> 
> Fwiw, I don't like Maildir for long-term storage at all, it's
> fine for volatile inboxes, but has the same problems as loose
> git objects which I don't like.

Yes, it's scattered over filesystem, which harms performance.
But, at least, I can use notmuch with it.

Right now, I need to run public-inbox-nttpd to be able to read the
archive, and public-inbox-httpd to search.

> > I would like to have a pointer, so I can implement this myself if
> > public-inbox don't want this feature.
> 
> I suggest l2md for now :)

Thanks, I'll look into it.

-- 
Danh

      parent reply	other threads:[~2020-04-26 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  4:37 How to Extract public-inbox v2 to Maildir Danh Doan
2020-04-26  6:05 ` Eric Wong
2020-04-26  6:07   ` Eric Wong
2020-04-26 14:19   ` Danh Doan [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=20200426141923.GC14800@danh.dev \
    --to=congdanhqx@gmail.com \
    --cc=e@yhbt.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).