From: Arun Isaac <arunisaac@systemreboot.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>, guix-devel@gnu.org
Subject: Re: `mumi send-email' means no more debbugs dance to send multiple patches
Date: Mon, 01 May 2023 23:47:40 +0100 [thread overview]
Message-ID: <87h6svd5yr.fsf@systemreboot.net> (raw)
In-Reply-To: <87y1mc3y6u.fsf@gmail.com>
> All the above could be handled at the level of git directly with the
> changes suggested in #58813, so I'd suggest we do this, which benefits
> everyone/everything relying on it.
Ah, I was not aware of #58813 and that this could be done at the level
of git. Good point! And, thanks for your work on #58813!
> But I think something extra that mumi send-email could do, which git
> can't (because it doesn't fetch the existing thread data), would be to
> CC all parties that have already commented in the corresponding thread
> (if the issue already exists). I think this is what John was going
> at.
Done now! I have sent patches to https://issues.guix.gnu.org/63215 . I
will push in a few days unless there are objections.
next prev parent reply other threads:[~2023-05-01 23:33 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
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 [this message]
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=87h6svd5yr.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=maxim.cournoyer@gmail.com \
/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).