From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Joey Pabalinas <joeypabalinas@gmail.com>,
Joe Perches <joe@perches.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 14:55:05 -0500 [thread overview]
Message-ID: <20181216195505.GB7732@pure.paranoia.local> (raw)
In-Reply-To: <20181216192135.hc7gykmwkfgil2j5@gmail.com>
On Sun, Dec 16, 2018 at 09:21:35AM -1000, Joey Pabalinas wrote:
> That was my first attempt, but the ducumentation for the public-inbox
> format is sort of terrible,
I'm surprised you think so, because it's basically a simple file called
"m" that is updated on each commit and contains the body of the
message.
> and after a few hours trying to convert it to Maildir I just gave up.
It's as easy as something like this:
for commit in $(git rev-list master); do:
git show $commit:m > maildir/new/$commit
done
You have to do it per each of the shards for the complete archive.
-K
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-12-16 19:56 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 [this message]
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
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=20181216195505.GB7732@pure.paranoia.local \
--to=konstantin@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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).