Subject: bug#65923: closed (Re: [mumi] after sending a new patch series, current issue should be set)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 19 Mar 2025 23:29:02 +0000

Your bug report

#65923: [mumi] after sending a new patch series, current issue should be set

which was filed against the mumi package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
65923: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65923
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: [mumi] after sending a new patch series, current issue should be set
From: Arun Isaac <[email-masked]>
To: [email-masked]
Cc: Maxim Cournoyer <[email-masked]>
Date: Wed, 19 Mar 2025 23:28:25 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

Done!
https://git.savannah.gnu.org/cgit/guix/mumi.git/commit/?id=1557a8c812968b63a1b85421eb3dd67a42919d00

It had to wait all this long for `mumi send-email' to work reliably!
Else, the added 15 minute delays for single patches would have been very
annoying.
https://issues.guix.gnu.org/74395

Subject: [mumi] after sending a new patch series, current issue should be set
From: Maxim Cournoyer <[email-masked]>
To: bug-guix <[email-masked]>
Date: Wed, 13 Sep 2023 13:27:19 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi,

Currently doing something like:
--8<---------------cut here---------------start------------->8---
$ mumi new
$ mumi send-email *.patch
(mumi queries new issue number from Debbugs)
(patches are sent)
$ mumi current
-> No current issue!
--8<---------------cut here---------------end--------------->8---

I'd expect the last 'mumi current' command to return the issue found
querying Debbugs at step 2.

-- 
Thanks,
Maxim