From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: How to wide-reply (email) to multiple people?
Date: Sun, 09 Dec 2018 18:56:48 +0100 [thread overview]
Message-ID: <87bm5ubn33.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87h8fmtxnn.fsf@ericabrahamsen.net>
Eric writes:
> I think he's trying to "rejoin" two branches with a message that replies
> to multiple other messages, like a git merge commit.
Ahh, thanks.
I don't know how the tree-drawing code handles that. I don't see why it
couldn't, but given it's called "tree", maybe it doesn't :-)
Also, I rarely see discussions join each other again, once they have
split.
Best regards,
Adam
--
"I went for the fireengines Adam Sjøgren
But they were all upside down" asjo@koldfront.dk
next prev parent reply other threads:[~2018-12-09 17:56 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
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 [this message]
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=87bm5ubn33.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--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).