unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Version 22.1.100 in Emacs Lisp Intro??
Date: Mon, 06 Nov 2006 21:38:58 +0100	[thread overview]
Message-ID: <m37iy8nwd9.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <8764dsy6ic.fsf@stupidchicken.com> (Chong Yidong's message of "Mon\, 06 Nov 2006 09\:49\:47 -0500")

Chong Yidong <cyd@stupidchicken.com> writes:

> storm@cua.dk (Kim F. Storm) writes:
>
>> The following change triggered some thoughs:
>>
>> +2006-11-04  Robert J. Chassell  <bob@rattlesnake.com>
>> +
>> +	* emacs-lisp-intro.texi: Replace 22.0.100 with	22.1.100.
>>
>> Since we use 22.0.50 for the CVS version, 22.0.90,... for pretests,
>> it seems quite non-intuitive for Emacs Lisp Intro to use 22.1.100
>> in an introductionary text.  
>>
>> Since most users will get a version 22.1.1 when then they build Emacs
>> from the tarball, it would IMO make more sense to use 22.1.1 in the
>> examples.
>
> We could update the `set-version' command in admin/admin.el, so that
> the Lispintro version number is automatically bumped each time a new
> pretest is rolled.  (The Emacs and Emacs Lisp manuals are already
> being bumped in this way.)

IMO the lisp intro should say 22.1 in the examples.  So I don't see a
need to do as you suggest.

The version number in file names used in the intro is of the form MAJOR.MINOR.BUILD

In contrast, the CVS / pretest versions uses MAJOR.MINOR.MICRO.BUILD

So 22.1.100 refers to build number 100 of 22.1

Bob already changes the intro to use a 22.1.1 (ie build number 1)
instead, and that's all that's needed.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-11-06 20:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  9:18 Version 22.1.100 in Emacs Lisp Intro?? Kim F. Storm
2006-11-06 14:49 ` Chong Yidong
2006-11-06 20:38   ` Kim F. Storm [this message]
2006-11-06 15:15 ` 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=m37iy8nwd9.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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).