From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: "Robin S. Socha" <robin-dated-1016459156.2abe03@socha.net>,
Ding <ding@gnus.org>,
webmasters@my.gnus.org, Justin Sheehy <justin@iago.org>
Subject: Re: Gnus FAQ maintainership
Date: Mon, 18 Mar 2002 12:12:57 +0100 [thread overview]
Message-ID: <rj1yeigmdi.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <vafy9gsplaf.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 16 Mar 2002 16:47:04 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I'm not doing any of the work, so I don't actually have a say in
> this, but IMVHO the FAQ should be maintained in Texinfo format simply
> so that it can be included in the Gnus manual.
And makeinfo can generate plain text, html and info from a Texinfo
document.
prev parent reply other threads:[~2002-03-18 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 21:08 Justin Sheehy
2002-03-15 14:27 ` Robin S. Socha
2002-03-15 15:50 ` Justin Sheehy
2002-03-15 16:32 ` Robin S. Socha
2002-03-16 15:47 ` Kai Großjohann
2002-03-18 11:12 ` Per Abrahamsen [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=rj1yeigmdi.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=ding@gnus.org \
--cc=justin@iago.org \
--cc=robin-dated-1016459156.2abe03@socha.net \
--cc=webmasters@my.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).