From: Joshua Branson <jbranso@dismail.de>
To: Mekeor Melire <mekeor@posteo.de>
Cc: 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 10:39:16 -0500 [thread overview]
Message-ID: <87wn75507v.fsf@dismail.de> (raw)
In-Reply-To: <87zgc2kix5.fsf@posteo.de> (Mekeor Melire's message of "Sun, 04 Dec 2022 20:16:02 +0000")
Mekeor Melire <mekeor@posteo.de> writes:
> 2022-11-16 / 23:41 / mekeor@posteo.de:
>> 2022-11-16 / 23:22 / jbranso@dismail.de:
>> > November 16, 2022 6:15 PM, "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.
>
>> > Would you mind writing this up and including it in the guix cookbook?
>>
>> Alright, I'll try to send a patch. I think I should change the
>> instructions in order to replace the unpackaged mb2md perl-script in
>> favor of the packaged mblaze tool. Afterwards, it should be straight
>> forward.
>
> I made a little shell script out of these instructions. You can find it
> attached. The script allows to either import a specified GNU
> mailing-list into a specified maildir, or update that maildir, beginning
> either from a specified YYYY-MM date or from the date of the latest
> message.
>
> For example, I used this command to initialize my mailing-list-maildirs:
>
> guix shell mblaze html-xml-utils -- sh -c 'for l in bug-guix
> guix-devel guix-patches help-guix; do ~/path/to/ugmltmd
> ~/path/to/mail/$l $l 2022-01; done'
>
> And I use the following command to update my mailing-list-maildirs:
>
> guix shell mblaze html-xml-utils -- sh -c 'for l in bug-guix
> guix-devel guix-patches help-guix; do ~/path/to/ugmltmd
> ~/path/to/mail/$l $l; done'
>
> I wonder if it still makes sense to add some instructions into the Guix
> cookbook. And if so, I wonder if this shell script should just be put
> there or if it should live in some public git repository somewhere.
>
> What do you think?
I would reach out to guix devel/guix-patches and try to put this little
code snippet in guix's source's /etc directory. Then add to the
cookbook explaining how to use it. Something like this would be
tremendously useful!
Thanks for working on it!
Joshua
next prev parent reply other threads:[~2022-12-05 15:39 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 [this message]
2022-12-05 8:45 ` zimoun
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=87wn75507v.fsf@dismail.de \
--to=jbranso@dismail.de \
--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).