unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: Please post older versions of GNU Emacs manuals on the web
Date: Sun, 03 Jan 2016 06:33:49 +0000	[thread overview]
Message-ID: <8760zbw4s2.fsf@violet.siamics.net> (raw)
In-Reply-To: <ade8e79f-0675-4bb2-8874-d83a7fa9f395@default> (Drew Adams's message of "Sat, 2 Jan 2016 09:19:04 -0800 (PST)")

>>>>> Drew Adams <drew.adams@oracle.com> writes:

[…]

 > Sure, the Wayback Machine is a great resource, and the Internet
 > Archive responsible for it is a great place to visit in San
 > Francisco.

 > But telling users to look to Internet archives (or to just google for
 > “defadvice emacs”) does not really answer my question of “Why not?”
 > or respond to my proposal.

	I see no reason we can’t do both: we can tell the users (or,
	rather, their UAs) to use the Wayback machine by providing links
	to the archived pages at http://gnu.org/s/emacs/manual/ – as
	well as all the Emacs documentation pages referenced there.
	With some effort, we could probably even link to the
	documentation for specific Emacs versions from there.

 > IMO we should offer Emacs users easy online access to the manuals for
 > older Emacs versions, the same way we offer them easy access to the
 > recent manuals and to both the recent and older versions of the
 > software.

 > This is the least we could do to help users and show them respect.
 > It should not be easier to find information about older releases of
 > Oracle, Apple, Microsoft, or IBM software than it is to find such
 > info for Emacs.

	I tend to agree that providing documentation for at least the
	latest releases of all the major versions is a well-established
	practice in the field, and I know of no reason why GNU in
	general – and not just Emacs – can’t follow it.

-- 
FSF associate member #7257  http://am-1.org/~ivan/      … 3013 B6A0 230E 334A



  reply	other threads:[~2016-01-03  6:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<1e249214-6831-4c2b-98a4-d16a6d1d7048@default>
     [not found] ` <<83a8onc3vc.fsf@gnu.org>
2016-01-02 17:19   ` Please post older versions of GNU Emacs manuals on the web Drew Adams
2016-01-03  6:33     ` Ivan Shmakov [this message]
     [not found] ` <<E1aFVL3-0000Fj-8h@fencepost.gnu.org>
2016-01-02 23:16   ` Drew Adams
2016-01-02 16:46 Drew Adams
2016-01-02 17:01 ` Eli Zaretskii
2016-01-02 17:11 ` John Wiegley
2016-01-02 17:19   ` Drew Adams
2016-01-04  3:15     ` Richard Stallman
2016-01-02 23:11 ` Richard Stallman
2016-01-03  3:57   ` John Wiegley
2016-01-03  4:09     ` Drew Adams
2016-01-03  4:18     ` raman
2016-01-03 10:55     ` David Kastrup
2016-01-03 16:34       ` Drew Adams
2016-01-03  2:07 ` Xue Fuqiao
2016-01-03  3:14 ` raman
2016-01-03  3:32   ` Drew Adams
2016-01-03  7:08 ` Teemu Likonen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760zbw4s2.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).