From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: C-d displays duplicated parts
Date: 28 Aug 1999 00:04:13 +0200 [thread overview]
Message-ID: <vaf672098yq.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: <vaf7lmgao3w.fsf@petty.cs.uni-dortmund.de>
Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> I must admit that I still don't understand why you need to introduce
> more parts.
I now verified the introducing-parts part as follows:
I wrote a message with the following contents:
,-----
| <#part>
| this is part one
| <#part type="message/rfc822">
| From: me
| To: you
| Subject: inner message
|
| test test
`-----
I sent it. I then went back and changed the "message/rfc822" into
"text/plain" and sent the changed message again.
I received two messages, and C-d on the first message showed this:
,-----
| +[27-Aug, 0b: -> Kai Großjoha] <* mixed> test MIME
| + [27-Aug, 0b: -> Kai Großjoha] <1 text>
| + [27-Aug, 0b: -> Kai Großjoha] <2 rfc822>
| [01-Jan, 0b: me ] <2 text> inner message
`-----
Whereas C-d on the second message showed this:
,-----
| +[27-Aug, 0b: -> Kai Großjoha] <* mixed> test MIME
| + [27-Aug, 0b: -> Kai Großjoha] <1 text>
| [27-Aug, 0b: me ] inner message
`-----
I think that pretty much proves my `a node is added' statement.
Can you explain why that node is added?
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-08-27 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-20 19:55 Vladimir Volovich
1999-07-21 1:59 ` Justin Sheehy
1999-07-21 7:44 ` Vladimir Volovich
1999-08-27 21:05 ` Lars Magne Ingebrigtsen
1999-08-27 21:29 ` François Pinard
1999-08-27 21:51 ` Kai Großjohann
1999-08-27 22:04 ` Kai Großjohann [this message]
1999-08-27 22:11 ` Lars Magne Ingebrigtsen
1999-08-27 22:16 ` Kai Großjohann
1999-08-27 22:31 ` Lars Magne Ingebrigtsen
1999-08-28 13:53 ` Kai Großjohann
1999-08-28 16:06 ` François Pinard
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=vaf672098yq.fsf@petty.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).