From: Vincent Legoll <vincent.legoll@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>,
Greg Hogan <code@greghogan.com>,
66703@debbugs.gnu.org
Subject: bug#66703: Broken link to Debbugs User Guide
Date: Sat, 14 Dec 2024 15:58:48 +0000 [thread overview]
Message-ID: <CAEwRq=r6DK5rvGtqU+yBb4bFs6_Zhck7xVZxLx1ugpqzoheO9g@mail.gmail.com> (raw)
In-Reply-To: <87r06a1dju.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Maxime,
On Sat, Dec 14, 2024 at 3:37 PM Maxim Cournoyer <maxim.cournoyer@gmail.com>
wrote:
>
> > Yes, I did not use the tool (mumi CLI ?) to reply, so I just sent to the
> > bug number
> > hoping it would reach the interested people. I think an easy CC list that
> > you can
> > copy/paste would be a nice UI feature for mumi web.
>
> Perhaps it was added later to mumi, but I'm pretty sure it now adds
> X-Debbugs-CC custom email headers with all the participants in the
> thread of the bug, at least it does for 'mumi send-email' (I just tried
> it to send a patch to an older issue thread).
>
Yes, I too am expecting mumi CLI to DTRT, but for the mumi web users,
the equivalent CC list that you can easily cutnpaste would be nice. That's
what I meant, the mumi web should strive to have similar features from
the CLI when it's not too hard, IMHO...
--
Vincent Legoll
[-- Attachment #2: Type: text/html, Size: 1482 bytes --]
next prev parent reply other threads:[~2024-12-14 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 14:51 bug#66703: Broken link to Debbugs User Guide Greg Hogan
2023-10-24 2:39 ` Maxim Cournoyer
2023-10-27 2:42 ` John Kehayias via Bug reports for GNU Guix
2023-10-31 15:19 ` Maxim Cournoyer
2024-12-09 2:12 ` John Kehayias via Bug reports for GNU Guix
2024-12-09 18:44 ` Vincent Legoll
2024-12-14 15:37 ` Maxim Cournoyer
2024-12-14 15:58 ` Vincent Legoll [this message]
2024-06-15 12:01 ` bug#66703: [PATCH] doc: Remove 'Debbugs User Guide' broken links Vincent Legoll
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='CAEwRq=r6DK5rvGtqU+yBb4bFs6_Zhck7xVZxLx1ugpqzoheO9g@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=66703@debbugs.gnu.org \
--cc=code@greghogan.com \
--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 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.