From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
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: Fri, 28 Apr 2023 09:59:05 -0400 [thread overview]
Message-ID: <87y1mc3y6u.fsf@gmail.com> (raw)
In-Reply-To: <87h6t2gpa2.fsf@systemreboot.net> (Arun Isaac's message of "Thu, 27 Apr 2023 01:08:37 +0100")
Hello,
Arun Isaac <arunisaac@systemreboot.net> writes:
> Hi John,
>
>> I just tried it out and it worked smoothly for sending 2 patches to an
>> existing bug. However, it was sent only directly to the bug address,
>> not being aware I guess of anyone that had submitted or since been
>> CC'ed to the thread.
>>
>> Is there anything we can do here? I learned about the useful "wide
>> reply" when using debbugs in Emacs and presumably mumi can/does know
>> about all addresses on the bug. So hopefully this wishlist item won't
>> be too difficult.
>
> This is definitely a nice feature to have. For now, I put in the other
> addresses as Cc when creating the patch using `git format-patch'. Should
> we build this feature into `mumi send-email' or should we create a
> separate `mumi format-patch' command that will create a patch with the
> correct Cc and with other necessary options passed to `git
> format-patch'? The other necessary options (think options like `-1 -a
> --base=auto' as recommended in the Guix manual at "(guix) Sending a
> Patch Series") could be configured in .mumi/config allowing different
> projects using mumi to recommend different options.
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.
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.
> Either way, patches to mumi are always welcome! ;-)
Thanks for this nice tool!
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-04-28 13:59 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 [this message]
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=87y1mc3y6u.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.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).