Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Garreau <galex-713@galex-713.eu>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: ding@gnus.org
Subject: Re: How to wide-reply (email) to multiple people?
Date: Sun, 09 Dec 2018 04:57:37 +0100	[thread overview]
Message-ID: <87ftv7pd1q.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <87efarn0ni.fsf@gmail.com> (Chris Marusich's message of "Sat, 08 Dec 2018 13:56:01 -0800")

This is a feature I’ve been using quite much, and I’d like its behavior
to be more logical toward redundancy of subjects too.

Btw, thanks for S V (didn’t know about it, I thought it would be the
default)!

Some (non-standard, I guess) feature I always wanted is true multiple
reply for emails: like, multiple message-ids in the in-reply-to, and
merging the references of all messages you reply too.  That way
threading becomes a true graph…

I did that some times, rarely.  The worse that happenned until now is
people interpreting it as thread stealing (though I changed the subject,
used Was:, and both subjects and messages were mine).  Would that break
a lot of clients?  How far would that go away from current standards (do
you believe a such thing could become standard one day?)?

I’d love to begin doing that and then making up some interface within
Summary that would display it graph-like like in git :D



  parent reply	other threads:[~2018-12-09  3:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 21:56 Chris Marusich
2018-12-08 22:26 ` Adam Sjøgren
2018-12-09  3:42   ` Chris Marusich
2018-12-09  3:57 ` Alexandre Garreau [this message]
2018-12-09 12:07   ` Adam Sjøgren
2018-12-09 13:17     ` Alexandre Garreau
2018-12-09 13:28       ` Alexandre Garreau
2018-12-09 13:44         ` Adam Sjøgren
2018-12-09 17:31           ` Eric Abrahamsen
2018-12-09 17:56             ` Adam Sjøgren
2018-12-09 13:41       ` Adam Sjøgren

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=87ftv7pd1q.fsf@portable.galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=cmmarusich@gmail.com \
    --cc=ding@gnus.org \
    /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.
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 NNTP newsgroup(s).