[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mummi wishlist: API using Message-ID

From: Julien Lepiller
Subject: Re: Mummi wishlist: API using Message-ID
Date: Mon, 06 Jun 2022 14:30:16 +0200
User-agent: K-9 Mail for Android

As long as the script shows it's trying and explains why it takes time, it should be fine. It could offer a --continue option too :)

On June 6, 2022 2:03:16 PM GMT+02:00, Ricardo Wurmus <> wrote:

Arun Isaac <> writes:

Once delpoyed to you can visit

This is great news! Using this, we should be able to implement a `mumi
send-email' command to easily send N patches to a new issue. Here is
how `mumi send-email' might be implemented:

1. Generate patches with `git format-patch --thread' so that there is a
Message-ID header.

2. Send the first patch to

3. Poll<message-id> to see if the first
patch has reached Debbugs/Mumi. Find the issue number of the new
issue that was created.

4. Send the remaining patches to the new issue.

This sounds like it could take quite some time, and the work it performs
is not transactional, so an impatient person cancelling it before
completion could end up with a bunch of “initial” emails without ever
sending the rest of the patches.

I think that maybe we should wean mumi off of debbugs and operate on
received email directly (using debbugs as a storage backend for the time


reply via email to

[Prev in Thread] Current Thread [Next in Thread]