guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] alist type error
Date: Wed, 04 Dec 2019 18:05:32 +0530	[thread overview]
Message-ID: <cu78sns8e0b.fsf@systemreboot.net> (raw)
In-Reply-To: <cu7blso8gz2.fsf@systemreboot.net>


[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]


> 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.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[-- Attachment #2: Type: text/plain, Size: 110 bytes --]

-- 
guile-email mailing list
guile-email@systemreboot.net
https://lists.systemreboot.net/listinfo/guile-email

WARNING: multiple messages have this Message-ID
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] alist type error
Date: Wed, 04 Dec 2019 18:05:32 +0530	[thread overview]
Message-ID: <cu78sns8e0b.fsf@systemreboot.net> (raw)
Message-ID: <20191204123532.WC26Sdu7_gL4-KJfOqZHn0-IdlDrkd4Pj5LVySSjO9w@z> (raw)
In-Reply-To: <cu7blso8gz2.fsf@systemreboot.net>

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]


> 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2019-12-04 13:52 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 [this message]
2019-12-04 12:35     ` Arun Isaac
2019-12-04 13:58     ` Ricardo Wurmus
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=cu78sns8e0b.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guile-email@systemreboot.net \
    --cc=rekado@elephly.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