From: Eric Wong <e@80x24.org>
To: Joey Pabalinas <joeypabalinas@gmail.com>
Cc: 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: Fri, 4 Jan 2019 01:35:22 +0000 [thread overview]
Message-ID: <20190104013522.stng6gwauwnr6wbi@starla> (raw)
In-Reply-To: <20181216195343.idnt2y5y5wjky5gu@gmail.com>
Joey Pabalinas <joeypabalinas@gmail.com> wrote:
> 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.
Sorry, I didn't notice this before. I started making some attempts
at improving documentation (among other things, when time permits)
to public-inbox:
https://public-inbox.org/meta/20190102083305.30473-1-e@80x24.org/
And without knowing anything about git or public-inbox, you can
get NNTP messages into Maildir or mboxrd pretty easily. Nothing
new to learn :)
I wrote a one-off Ruby years ago (before public-inbox) for
converting slrnspools to Maildir (sample slrnpull.conf below).
But yeah, I wouldn't recommend 3M+ messages in a Maildir...
==> slrnspool2maildir <==
#!/usr/bin/ruby
require 'socket'
require 'fileutils'
HOSTNAME = Socket.gethostname
usage = "Usage #$0 <spooldir> <maildir>"
spooldir = ARGV[0] or abort usage
maildir = ARGV[1] or abort usage
f = base = nil
nr = 0
%w(cur new tmp).each { |x| FileUtils.mkpath("#{maildir}/#{x}") }
Dir.glob("#{spooldir}/*").each do |src|
File.file?(src) or next
base = File.basename(src)
dest = "#{maildir}/new/#{Time.now.to_i}_#{base}_0.#{HOSTNAME}:2,"
begin
File.link(src, dest)
rescue Errno::EEXIST
warn "#{dest} already exists"
next
end
File.unlink(src)
end
__END__
==> slrnpull.conf <==
# group_name max expire headers_only
inbox.com.example.news.group.name 1000000000 1000000000 0
# usage: slrnpull -d $PWD -h news.example.com --no-post
# Wouldn't be hard to script something using Net::NNTP in Perl
# to write directly to Maildirs, either.
next prev parent reply other threads:[~2019-01-04 1:35 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
2019-01-04 1:35 ` Eric Wong [this message]
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=20190104013522.stng6gwauwnr6wbi@starla \
--to=e@80x24.org \
--cc=gregkh@linuxfoundation.org \
--cc=joeypabalinas@gmail.com \
--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).