From: "Владимир Волович" <aaa@vsu.ru>
Cc: "Владимир Волович" <ccc@vsu.ru>, ding@gnus.org
Subject: bug in gnus
Date: 01 Oct 2000 13:53:47 +0400 [thread overview]
Message-ID: <eyitrcevkk.fsf@video.uic.vsu.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
Hi!
When following up to this message in a summary buffer (F),
i get the following headers prepared (which are correct):
To: Владимир Волович <aaa@vsu.ru>
Cc: Владимир Волович <bbb@vsu.ru>, Владимир Волович <ccc@vsu.ru>,
ding@gnus.org
but if i first press C-d, and then followup to the whole pessage or to
any of the parts, i get only
To: Владимир Волович <aaa@vsu.ru>
(and no other emails).
[-- Attachment #2: Type: text/plain, Size: 25 bytes --]
this is the second part
next reply other threads:[~2000-10-01 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-01 9:53 Владимир Волович [this message]
2000-10-01 13:16 ` ShengHuo ZHU
2000-10-01 16:27 ` Vladimir Volovich
-- strict thread matches above, loose matches on Subject: below --
2000-09-29 12:43 Владимир Волович
2000-09-29 13:23 ` ShengHuo ZHU
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=eyitrcevkk.fsf@video.uic.vsu.ru \
--to=aaa@vsu.ru \
--cc=ccc@vsu.ru \
--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).