From: Ted Zlatanov <tzz@lifelogs.com>
To: <ding@gnus.org>
Subject: Re: References to my.gnus.org/FAQ
Date: Mon, 14 Jun 2010 14:18:23 -0500 [thread overview]
Message-ID: <87k4q1whhc.fsf@lifelogs.com> (raw)
In-Reply-To: <m3mxuy3cjn.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Sun, 13 Jun 2010 20:25:32 +0000")
On Sun, 13 Jun 2010 20:25:32 +0000 Tim Landscheidt <tim@tim-landscheidt.de> wrote:
TL> I know; I meant are there output options that the Docbook
TL> format offers that are *not* feasible with Texinfo and that
TL> we consider valuable?
Yeah, I think we should only continue with the Texinfo output. Sorry I
misunderstood.
>> I'm not sure what gnus.cvs.sourceforge.net has. The Gnus CVS repo we
>> used for the Git import had texi/gnus-faq.texi with what seems like a
>> reasonable VC log. Considering the age of the FAQ, we should either
>> clean it up or move it to be part of the manual IMHO.
TL> The issue would have been the changes done before and be-
TL> tween imports from SourceForge to the Gnus CVS repository.
TL> But with Frank's mail that's done. Cleaning up the FAQ is of
TL> course still a nice idea :-).
I'd be happiest putting the FAQ in the manual so it can cross-reference
concepts and sections, and so we don't have to worry about the Docbook
format anymore. Frank, Tim, do you think that's reasonable?
Ted
next prev parent reply other threads:[~2010-06-14 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 23:47 Tim Landscheidt
2010-06-05 2:26 ` Ted Zlatanov
2010-06-09 23:52 ` Tim Landscheidt
2010-06-13 2:53 ` Ted Zlatanov
2010-06-13 20:25 ` Tim Landscheidt
2010-06-14 19:18 ` Ted Zlatanov [this message]
2010-06-14 20:35 ` Tim Landscheidt
2010-06-15 6:22 ` Reiner Steib
2010-07-01 14:08 ` Ted Zlatanov
2010-06-15 7:09 ` Frank Schmitt
2010-06-13 10:11 ` Frank Schmitt
2010-06-13 20:29 ` Tim Landscheidt
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=87k4q1whhc.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).