From: Joey Pabalinas <joeypabalinas@gmail.com>
To: Joey Pabalinas <joeypabalinas@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernelnewbies@kernelnewbies.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [RFC] LKML Archive in Maildir Format
Date: Sun, 16 Dec 2018 09:53:43 -1000 [thread overview]
Message-ID: <20181216195343.idnt2y5y5wjky5gu@gmail.com> (raw)
In-Reply-To: <20181216194649.GA7732@pure.paranoia.local>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
On Sun, Dec 16, 2018 at 02:46:49PM -0500, Konstantin Ryabitsev wrote:
> On Sun, Dec 16, 2018 at 09:06:39AM -1000, Joey Pabalinas wrote:
> > I spent a lot of time trying to find an LKML archive in Maildir format
> > that I could use for local searches with nutmuch or something, but all
> > the links I was able to find were all dead.
> >
> > I ended up just compiling one myself and I currently host it at:
> >
> > https://alyptik.org/lkml.tar.xz
>
> You seem to have duplicated a lot of effort that has already been done
> to compile the archive on lore.kernel.org.
Absolutely correct, haha.
>
> > It's possible I'm the only weirdo who finds this kind of thing useful, but
> > I figured I should share it just in case I'm not.
>
> The maildir format is kind of terrible for LKML, because having millions
> of messages in a single directory is very hard on the underlying FS. If
> you break it up into multiple folders, then it becomes difficult to
> search. This is the main reason why we have chosen to go with the
> public-inbox format, which solves both of these problems and allows for
> a very efficient archive updating and replication using git.
>
> > It's about 1.1 million files, I was wondering if anyone had an idea of a
> > better way to host this? I've tried Github and GitLab, but they don't
> > appreciate repos with that many files, hah.
>
> Like I said, you seem to be going down the road we've already tried and
> rejected. :)
Yes, I had a strong suspicion I might be the only crazy person who prefers this
kind of format :)
My only comment on the public-mailbox choice is that the documentation
is very sparse and erratic. Myself and a couple other people just
couldn't figure out how to convert that format to Maildir or some other
format you could feed into a reader like neomutt.
Do you have any advice on how to convert those public-inbox files
correctly?
--
Cheers,
Joey Pabalinas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-16 19:53 UTC|newest]
Thread overview: 14+ 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-18 20:26 ` Jasper Spaans
2018-12-18 22:53 ` Joey Pabalinas
2018-12-16 19:46 ` Konstantin Ryabitsev
2018-12-16 19:53 ` Joey Pabalinas [this message]
2019-01-04 1:35 ` Eric Wong
2019-03-05 20:48 ` Bjorn Helgaas
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=20181216195343.idnt2y5y5wjky5gu@gmail.com \
--to=joeypabalinas@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelnewbies@kernelnewbies.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).