From: Bjorn Helgaas <bhelgaas@google.com>
To: Eric Wong <e@80x24.org>
Cc: Jasper Spaans <j@jasper.es>,
kernelnewbies@kernelnewbies.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Biederman <ebiederm@xmission.com>,
Joey Pabalinas <joeypabalinas@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [RFC] LKML Archive in Maildir Format
Date: Tue, 5 Mar 2019 14:48:36 -0600 [thread overview]
Message-ID: <CAErSpo5a2oO=5byEuA5AouS=kBmj7ihw2EVYAvJcdti29Tf1HQ@mail.gmail.com> (raw)
In-Reply-To: <20190104013522.stng6gwauwnr6wbi@starla>
OK, so I understand how to clone archives from lore.kernel.org and how
to convert a git archive to a maildir (thanks, Konstantin!)
What I *don't* understand is how to effectively read this locally.
Ideally I'd like to run mutt, possibly with notmuch for indexing. But
a maildir with 3M files seems impractical. I did actually try it
(without notmuch), but it takes mutt about 5 minutes to start up. And
the maildir is about 23G, compared with 7.5G for the git archive.
Any pointers? I guess there's no mutt backend that can read a
public-inbox archive directly?
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-03-05 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 19:06 [RFC] LKML Archive in Maildir Format Joey Pabalinas
2018-12-16 19:17 ` Joe Perches
2018-12-16 19:21 ` Joey Pabalinas
2018-12-16 19:55 ` Konstantin Ryabitsev
2018-12-16 21:55 ` Joey Pabalinas
2018-12-16 19:46 ` Konstantin Ryabitsev
2018-12-16 19:53 ` Joey Pabalinas
[not found] ` <20190104013522.stng6gwauwnr6wbi@starla>
2019-03-05 20:48 ` Bjorn Helgaas [this message]
2019-03-05 23:26 ` Eric Wong
2019-03-06 20:50 ` Bjorn Helgaas
2019-03-07 3:44 ` Eric Wong
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='CAErSpo5a2oO=5byEuA5AouS=kBmj7ihw2EVYAvJcdti29Tf1HQ@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=e@80x24.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=j@jasper.es \
--cc=joeypabalinas@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).