From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Labels/Annotations per message
Date: 14 Aug 2000 23:10:52 +0200 [thread overview]
Message-ID: <vafd7jbo8f7.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: =?iso-8859-1?q?Fran=E7ois?= Pinard's message of "14 Aug 2000 11:52:54 -0400"
On 14 Aug 2000, François Pinard wrote:
> When `B m'ing or `B c'ing articles, annotations should move or be
> duplicated accordingly. The sad thing is that it will not work when
> moving articles into, and later out from, Babyl files...
Why not? I thought one of the niceties of the babyl format was that
it allowed adding extra information to messages?
As a last resort, the annotations could be put in X-Gnus-* headers.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2000-08-14 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-13 12:20 Pavel Janík ml.
2000-08-13 17:07 ` Lars Magne Ingebrigtsen
2000-08-13 19:13 ` Karl Eichwalder
2000-08-14 15:52 ` François Pinard
2000-08-14 21:10 ` Kai Großjohann [this message]
2000-08-13 19:26 ` Kai Großjohann
2000-08-13 19:50 ` Lars Magne Ingebrigtsen
2000-08-14 21:09 ` Kai Großjohann
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=vafd7jbo8f7.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).