From: zimoun <zimon.toutoune@gmail.com>
To: Mekeor Melire <mekeor@posteo.de>, help-guix <help-guix@gnu.org>
Subject: Re: This is how you import a mailing list archives (e.g. guix-patches) into mu4e
Date: Mon, 05 Dec 2022 09:45:41 +0100 [thread overview]
Message-ID: <864jua5jd6.fsf@gmail.com> (raw)
In-Reply-To: <878rka8pcj.fsf@posteo.de>
Hi,
On Wed, 16 Nov 2022 at 23:04, Mekeor Melire <mekeor@posteo.de> wrote:
> you might want to import a mailing-list-archive into mu4e. E.g. because
> debbugs.el is slow, you might want to import the archives of the
> guix-patches mailing list. This is how to do so.
Personally, I use “git clone” from a public-inbox instance [1].
git clone --mirror https://yhetil.org/guix-patches/1 \
guix-patches/git/1.git
where ’1’ can be also replace by ’0’ for the very old ones.
Then the conversion from Git commit to maildir is done by a small script
[2], where all the job reads:
--8<---------------cut here---------------start------------->8---
# Extract the message from each commit in the range and store it
# in the Maildir for notmuch to consume.
$git rev-list $range | while read sha; do
# XXXX: fatal: path 'm' does not exist in <commit>
# and it can also raise issues with notmuch, as:
# Note: Ignoring non-mail file: $maildir/new/$sha
$git show $sha:m > $maildir/new/$sha
done
--8<---------------cut here---------------end--------------->8---
(Maybe better could be done and more robust are around.)
Even, the same can be used for reading Guix mailing lists. New messages
are gotten with “git fetch”.
1: <https://yhetil.org/guix-patches/>
2: <https://gitlab.com/zimoun/my-conf/-/blob/master/.local/bin/sync-public-inboxes.sh#L60-67>
Cheers,
simon
next prev parent reply other threads:[~2022-12-05 9:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 23:04 This is how you import a mailing list archives (e.g. guix-patches) into mu4e Mekeor Melire
2022-11-16 23:22 ` jbranso
2022-11-16 23:41 ` Mekeor Melire
2022-12-04 20:16 ` Mekeor Melire
2022-12-05 15:39 ` Joshua Branson
2022-12-05 8:45 ` zimoun [this message]
2022-12-05 21:43 ` Mekeor Melire
2022-12-06 11:33 ` zimoun
2022-12-07 2:27 ` Mekeor Melire
2022-12-07 10:33 ` zimoun
2022-12-06 1:03 ` Kyle Meyer
2022-12-06 12:03 ` zimoun
2022-12-07 2:02 ` Kyle Meyer
2022-12-07 10:38 ` zimoun
2022-12-07 2:19 ` Mekeor Melire
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864jua5jd6.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=mekeor@posteo.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).