From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Buffer called *sent wide reply to TG <x@example.com>* but he was not one of the recipients
Date: Fri, 02 Aug 2013 14:44:33 +0200 [thread overview]
Message-ID: <m31u6c1cum.fsf@stories.gnus.org> (raw)
In-Reply-To: <8738qsfrva.fsf@jidanni.org>
jidanni@jidanni.org writes:
> Well that buffer name is now changed to be called
> *sent wide reply to TG <thatguy@example.com>*
It just changes the "unsent" to "sent".
--
(domestic pets only, the antidote for overdose, milk.)
No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
next prev parent reply other threads:[~2013-08-02 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 7:56 jidanni
2013-08-02 12:44 ` Lars Magne Ingebrigtsen [this message]
2013-08-03 3:28 ` Eric Abrahamsen
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=m31u6c1cum.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--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).