unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org
Subject: Re: Problem building emacs-lisp-intro.dvi.
Date: Tue, 22 Aug 2006 17:51:13 +0000 (UTC)	[thread overview]
Message-ID: <m1GFaPB-0004SKC@rattlesnake.com> (raw)
In-Reply-To: <85ac5x2hdo.fsf@lola.goethe.zz> (message from David Kastrup on Tue, 22 Aug 2006 12:29:23 +0200)

    Backward compatibility with _what_?  What relevance has the release
    date of Emacs 20 with some presumed backward compatibility of Emacs
    22.1 documentation?

It is not the documentation I am concerned with, but with the problem
that some people possibly may not have an updated Texinfo
distribution.  I figured that the release date of Emacs 20, which I
had information about, was a good enough time target even if it is not
related directly to the Texinfo distribution.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  reply	other threads:[~2006-08-22 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 11:19 Problem building emacs-lisp-intro.dvi Lute Kamstra
2006-08-21 14:50 ` Robert J. Chassell
2006-08-21 15:24   ` Lute Kamstra
2006-08-21 19:11     ` Robert J. Chassell
2006-08-21 21:26       ` Lute Kamstra
2006-08-22  0:45         ` Robert J. Chassell
2006-08-22  1:29           ` Eli Zaretskii
2006-08-22  7:53           ` David Kastrup
2006-08-22 10:26             ` Robert J. Chassell
2006-08-22 10:29               ` David Kastrup
2006-08-22 17:51                 ` Robert J. Chassell [this message]
2006-08-23 15:49               ` Eli Zaretskii
2006-08-23 16:26                 ` Andreas Schwab
2006-08-23 19:11                   ` Robert J. Chassell
2006-08-22 10:30             ` Robert J. Chassell

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=m1GFaPB-0004SKC@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --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).