From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Jon Cast Newsgroups: gmane.emacs.devel Subject: Re: No calc in pretest? Date: Tue, 02 Jul 2002 19:33:35 -0500 Sender: emacs-devel-admin@gnu.org Message-ID: <200207030033.g630XZM20263@d-ip-129-15-78-125.cs.ou.edu> References: NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1025656559 14569 127.0.0.1 (3 Jul 2002 00:35:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 3 Jul 2002 00:35:59 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17PY7i-0003mr-00 for ; Wed, 03 Jul 2002 02:35:58 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17PYCz-0001IE-00 for ; Wed, 03 Jul 2002 02:41:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17PY7t-0002Nt-00; Tue, 02 Jul 2002 20:36:09 -0400 Original-Received: from d-ip-129-15-78-125.cs.ou.edu ([129.15.78.125]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17PY5d-00028F-00 for ; Tue, 02 Jul 2002 20:33:50 -0400 Original-Received: from ou.edu (jcast@localhost) by d-ip-129-15-78-125.cs.ou.edu (8.11.6/8.11.6) with ESMTP id g630XZM20263; Tue, 2 Jul 2002 19:33:35 -0500 X-Authentication-Warning: d-ip-129-15-78-125.cs.ou.edu: jcast owned process doing -bs Original-To: bob@rattlesnake.com In-Reply-To: Message from "Robert J. Chassell" of "Tue, 02 Jul 2002 21:30:55 -0000." Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:5379 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5379 Robert J. Chassell" wrote: > The change that seems to have caused all this discussion is the idea > of having two tracks, a `bug-fix' track, and a `new-features' track. > In the past, there was only one track, which included both bug fixes > and new features. There /are/ two tracks already. The problem is, they're interleaved, so you can't tell which track a particular release is on. The discussion is simply looking for a way to dis-entangle the tracks. > -- > Robert J. Chassell bob@rattlesnake.com > Rattlesnake Enterprises http://www.rattlesnake.com Jon Cast