From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Support for slrn-style verbatim marks
Date: Wed, 28 Sep 2005 11:48:27 +0200 [thread overview]
Message-ID: <v9d5mtjzf8.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4m4q85g9ka.fsf@jpl.org>
On Wed, Sep 28 2005, Katsumi Yamaoka wrote:
> I'm not familiar with the verbatim parts, so I leave it to your
> decision. BTW, is it necessary to put `gnus' in the name of the
> part type? (I feel `x-verbatim' is sufficient.)
For me, either one is fine. See my reply to Simon. If more people
prefer "x-verbatim" we can change it (maybe let's a couple of days).
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-09-28 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:31 Reiner Steib
2005-09-26 11:06 ` Adam Sjøgren
2005-09-26 18:08 ` Reiner Steib
2005-09-26 19:15 ` Adam Sjøgren
2005-09-26 21:09 ` Reiner Steib
2005-09-27 2:17 ` Katsumi Yamaoka
2005-09-27 12:53 ` Reiner Steib
2005-09-27 15:04 ` Simon Josefsson
2005-09-27 16:18 ` Reiner Steib
2005-09-28 9:43 ` Simon Josefsson
2005-09-28 3:23 ` Katsumi Yamaoka
2005-09-28 9:48 ` Reiner Steib [this message]
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=v9d5mtjzf8.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).