From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: #v+, #v-
Date: Sat, 14 Feb 2004 23:18:01 +0100 [thread overview]
Message-ID: <87ad3ljofa.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <?fnord?874qttzetu.fsf@ID-97657.usr.dfncis.de>
lawrence mitchell <s0198183+ding@sms.ed.ac.uk> writes:
> I believe they're not supported in other mail/newsreaders
> though.
Well, anyone up to doing it for Gnus? Sounds like a cool feature. We
*do* already have MIME multiparts, but one feature more, what can it
hurt...
Kai
next prev parent reply other threads:[~2004-02-14 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 17:00 nnmaildir Thomas Schwinge
2004-02-11 17:42 ` nnmaildir Paul Jarc
2004-02-11 22:05 ` nnmaildir Thomas Schwinge
2004-02-11 23:23 ` nnmaildir Paul Jarc
2004-02-12 14:35 ` nnmaildir Thomas Schwinge
2004-02-12 16:36 ` nnmaildir Paul Jarc
2004-02-12 22:45 ` nnmaildir Thomas Schwinge
2004-02-12 22:57 ` nnmaildir Paul Jarc
2004-02-13 14:02 ` nnmaildir Thomas Schwinge
2004-02-14 3:34 ` nnmaildir Paul Jarc
2004-02-14 18:26 ` nnmaildir Kai Grossjohann
2004-02-14 18:38 ` #v+, #v- (was: nnmaildir) lawrence mitchell
2004-02-14 22:18 ` Kai Grossjohann [this message]
2004-02-15 3:33 ` #v+, #v- Karl Pflästerer
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=87ad3ljofa.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.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).