From: Ricardo Wurmus <rekado@elephly.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: Josselin Poiret <dev@jpoiret.xyz>, guix-devel@gnu.org
Subject: Re: `mumi send-email' means no more debbugs dance to send multiple patches
Date: Tue, 25 Apr 2023 16:44:29 +0200 [thread overview]
Message-ID: <87v8hkuiid.fsf@elephly.net> (raw)
In-Reply-To: <874jp4i1vu.fsf@systemreboot.net>
Arun Isaac <arunisaac@systemreboot.net> writes:
> The mumi server fetches emails from the debbugs server using a periodic
> rsync. This happens once every few minutes (< 5 minutes)[1]. After
> sending the first email, `mumi send-email' polls the mumi server once
> every minute to see if the email has reached the mumi server. `mumi
> send-email' retries this poll for a maximum of 15 times before giving
> up.
This could be changed. We don’t need to wait for the email to arrive on
the mumi server; could we ask debbugs directly for the email? (If we
can’t ask for the mail we could ask for newest bugs and check if that
contains the email.)
--
Ricardo
next prev parent reply other threads:[~2023-04-25 14:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:12 `mumi send-email' means no more debbugs dance to send multiple patches Arun Isaac
2023-04-24 18:17 ` (
2023-04-24 20:08 ` Josselin Poiret
2023-04-25 12:26 ` Arun Isaac
2023-04-25 14:44 ` Ricardo Wurmus [this message]
2023-04-26 23:51 ` Arun Isaac
2023-04-25 16:26 ` Josselin Poiret
2023-04-26 23:57 ` Arun Isaac
2023-04-27 8:49 ` Josselin Poiret
2023-05-01 23:37 ` Arun Isaac
2023-04-26 10:12 ` Andreas Enge
2023-04-27 0:33 ` mumi web server bugs [was "`mumi send-email' means no more debbugs dance to send multiple patches"] Arun Isaac
2023-04-26 21:27 ` `mumi send-email' means no more debbugs dance to send multiple patches John Kehayias
2023-04-27 0:08 ` Arun Isaac
2023-04-28 13:59 ` Maxim Cournoyer
2023-05-01 22:47 ` Arun Isaac
2023-05-02 12:41 ` Maxim Cournoyer
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=87v8hkuiid.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=arunisaac@systemreboot.net \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).