From: Dan Christensen <jdc@jhu.edu>
Cc: ding@gnus.org
Subject: Re: strange behaviour when `B c'ing an empty article
Date: Wed, 06 Oct 1999 20:26:11 -0400 [thread overview]
Message-ID: <87g0zoc8yk.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Shenghuo ZHU's message of "06 Oct 1999 19:24:09 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> >>>>> "Dan" == Dan Christensen <jdc@jhu.edu> writes:
>
> [...]
>
> Dan> When I do the same thing with the second article attached below,
> Dan> everything is fine. Could it have to do with the fact that the
> Dan> first article is empty?
>
> [...]
>
> I guess I just fixed it.
>
> The patch follows and has been committed.
I don't see any change in the behaviour.
Dan
--
Dan Christensen
jdc@math.jhu.edu
next prev parent reply other threads:[~1999-10-07 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-06 20:57 Dan Christensen
1999-10-06 23:24 ` Shenghuo ZHU
1999-10-07 0:26 ` Dan Christensen [this message]
1999-10-07 3:20 ` Shenghuo ZHU
1999-10-07 5:07 ` Dan Christensen
1999-10-07 5:51 ` Shenghuo ZHU
1999-10-07 15:37 ` Dan Christensen
1999-10-07 21:15 ` Shenghuo ZHU
1999-10-07 21:44 ` Dan Christensen
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=87g0zoc8yk.fsf@chow.mat.jhu.edu \
--to=jdc@jhu.edu \
--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).