From: Ricardo Wurmus <rekado@elephly.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] alist type error
Date: Wed, 04 Dec 2019 14:58:47 +0100 [thread overview]
Message-ID: <87muc8dwfc.fsf@elephly.net> (raw)
In-Reply-To: <cu78sns8e0b.fsf@systemreboot.net>
Arun Isaac <arunisaac@systemreboot.net> writes:
>> Meanwhile, I should set up some kind of "continuous testing" where all
>> mails in guix-patches are periodically parsed and crashes reported to
>> me, if any. Does mumi have any convenient API to fetch all emails from
>> guix-patches? I will look at the mumi source code myself, but if you
>> have any quick pointers, that would help.
>
> I just realized I could download mboxes from
> https://lists.gnu.org/archive/mbox/guix-patches/ and keep synchronizing
> them. That should be enough for my continuous testing purposes.
That’s what Guile Debbugs does as well.
--
Ricardo
next prev parent reply other threads:[~2019-12-04 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 10:10 Ricardo Wurmus
2019-12-04 11:31 ` Arun Isaac
2019-12-04 11:31 ` Arun Isaac
2019-12-04 12:35 ` Arun Isaac
2019-12-04 12:35 ` Arun Isaac
2019-12-04 13:58 ` Ricardo Wurmus [this message]
2019-12-05 9:29 ` Ricardo Wurmus
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=87muc8dwfc.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
/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