all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 65746-done@debbugs.gnu.org
Subject: [bug#65746] [PATCH] doc: Document mumi command-line interface.
Date: Thu, 07 Sep 2023 08:52:55 -0400	[thread overview]
Message-ID: <87fs3qno0o.fsf@gmail.com> (raw)
In-Reply-To: <87ledi1s0g.fsf@systemreboot.net> (Arun Isaac's message of "Thu,  07 Sep 2023 06:17:35 +0100")

Hi Arun,

Arun Isaac <arunisaac@systemreboot.net> writes:

> Hi Maxim,
>
> Thanks for pushing the patch. I also feel that "(guix) Sending a Patch
> Series" should be rewritten. Currently, it mentions that `git
> send-email' is the *best* way to send patches. It should now be only
> listed as one of two ways with `mumi send-email' being the preferred
> option since it is easier and less cognitive overhead to use.
>
> WDYT? Shall I send another patch about this?

I think it'd be beneficial to plug the 'mumi' command there yes; I agree
that it should be preferred to a plain 'git send-email' given it knows
to CC all participants in the conversation (until Debbugs can be taught
to do that itself (i.e. subscribe all participants to new mails sent to
NNNNN@debbugs.gnu.org)).  Maybe our .patman config could changed to use
'mumi send-email' as well, instead of 'git send-email' (or prefer it,
then fall-back to git send-email, maybe with a message).

-- 
Thanks,
Maxim




      reply	other threads:[~2023-09-07 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 21:31 [bug#65746] [PATCH] doc: Document mumi command-line interface Arun Isaac
2023-09-06  3:41 ` bug#65746: " Maxim Cournoyer
2023-09-07  5:17   ` [bug#65746] " Arun Isaac
2023-09-07 12:52     ` Maxim Cournoyer [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fs3qno0o.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=65746-done@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.