From: "Greg Stark" <stark@mit.edu>
To: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Gnus and GMail coexistence: need manual section
Date: Tue, 16 Sep 2008 13:44:30 +0100 [thread overview]
Message-ID: <407d949e0809160544m2707e542s4b2ab102a9daaabc@mail.gmail.com> (raw)
In-Reply-To: <86fxo1padk.fsf@lifelogs.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
> TZ> Should the link be in the manual? Should the manual freeze this
> TZ> information? I can see both sides of the argument but it seems that
> TZ> freezing the information *and* providing the URL would be technically
> TZ> best but also most confusing to the user.
>
> Ping? I'd like some opinions please. This is about how the Gnus manual
> coexists with emacswiki.org and similar sites, not just about GMail, so
> I don't want to make the decision on my own.
What's particular about the situation with GMail is that the manual would be
freezing documentation about something other than Gnus. If GMail changed
(and it does change quite frequently -- it's still in beta after all...)
then the documentation would be wrong. Not just out of date like
documentation for september Gnus or quassia Gnus is -- that documentation is
still accurate as far as it describes those versions -- it would be
incorrect even about the same version it was written for.
[-- Attachment #2: Type: text/html, Size: 1294 bytes --]
next prev parent reply other threads:[~2008-09-16 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 15:12 Ted Zlatanov
2008-09-07 23:27 ` Eric Schulte
2008-09-08 15:42 ` Ted Zlatanov
2008-09-15 17:49 ` Ted Zlatanov
2008-09-16 12:44 ` Greg Stark [this message]
2008-09-16 19:08 ` Ted Zlatanov
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=407d949e0809160544m2707e542s4b2ab102a9daaabc@mail.gmail.com \
--to=stark@mit.edu \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).