From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Robert J. Chassell" Newsgroups: gmane.emacs.devel Subject: Re: [jerome.marant@free.fr: Re: Possible help with stable Emacs releases.] Date: Thu, 30 Sep 2004 15:40:18 +0000 (UTC) Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <1096291271.415813c757a26@imp6-q.free.fr> <20040927134714.GA20012@fencepost> <87hdphx91c.fsf@trouble.defaultvalue.org> <87655wswkv.fsf@trouble.defaultvalue.org> <1096489325.415b196d95987@imp3-q.free.fr> <200409300053.i8U0rWh20758@raven.dms.auburn.edu> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1096559243 26550 80.91.229.6 (30 Sep 2004 15:47:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 30 Sep 2004 15:47:23 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 30 17:47:10 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CD39B-0004wh-00 for ; Thu, 30 Sep 2004 17:47:09 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CD3FZ-0002MN-Qq for ged-emacs-devel@m.gmane.org; Thu, 30 Sep 2004 11:53:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CD39X-0000H7-Lc for emacs-devel@gnu.org; Thu, 30 Sep 2004 11:47:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CD39W-0000Fz-7S for emacs-devel@gnu.org; Thu, 30 Sep 2004 11:47:30 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CD39V-0000En-L0 for emacs-devel@gnu.org; Thu, 30 Sep 2004 11:47:29 -0400 Original-Received: from [69.168.110.189] (helo=rattlesnake.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CD32e-00040R-Hf for emacs-devel@gnu.org; Thu, 30 Sep 2004 11:40:24 -0400 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.115) Thu, 30 Sep 2004 15:40:18 +0000 (UTC) Original-To: emacs-devel@gnu.org In-reply-to: (message from Miles Bader on Thu, 30 Sep 2004 10:25:21 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:27717 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:27717 > After grepping for `emacs-version', it appears that changing the > current convention would require checking a surprisingly *huge* > amount of code. Can we not just increment the last component of the existing three-component version number? Right now, emacs/lisp/version.el says (defconst emacs-version "21.3.50" "\ Version numbers of this version of Emacs.") Could not that be incremented to "21.3.51" for a bug fix release? (Or better yet, have the release be "21.4.0" and the bug fix releases be "21.4.1", "21.4.2", etc; this would enable us to continue to specify a 50 for the next version's CVS trunk and a 90 for the pretest, as in "21.4.50". ... Of course, I presume fewer than 50 bug fix releases before a minor or major version number increment .... :) Let's refer to the existing third component as the tertiant, with its adjective being `tertiary'. If for whatever reason, we need to specify a variable then it would be the third of this sequence; emacs-major-version emacs-minor-version emacs-tertiary-version as in (defconst emacs-tertiary-version (progn (string-match "\\(^[0-9]+\\.\\([0-9]+\\).\\([0-9]+\\)\\)" emacs-version) (string-to-int (match-string 3 emacs-version))) "Version number of the third component of emacs-version.") -- Robert J. Chassell bob@rattlesnake.com GnuPG Key ID: 004B4AC8 http://www.rattlesnake.com http://www.teak.cc