From xemacs-m  Fri Apr  4 08:23:42 1997
Received: from amber.vis-av.com (amber.vis-av.com [206.119.44.2])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id IAA14721
	for <xemacs-beta@xemacs.org>; Fri, 4 Apr 1997 08:23:41 -0600 (CST)
Received: (from derrell@localhost)
          by amber.vis-av.com (8.8.5/8.8.4)
	  id JAA12617; Fri, 4 Apr 1997 09:23:32 -0500 (EST)
Date: Fri, 4 Apr 1997 09:23:32 -0500 (EST)
Message-Id: <199704041423.JAA12617@amber.vis-av.com>
From: Derrell Lipman <derrell@vis-av.com>
To: tor@spacetec.no (Tor Arntsen)
Cc: xemacs-beta@xemacs.org (XEmacs Beta List)
Subject: Re: 19.15 future
In-Reply-To: <199704041046.MAA01185@pallas.spacetec.no>
References: <shelton@icd.teradyne.com>
	<199704041046.MAA01185@pallas.spacetec.no>
X-Mailer: VM 6.22 under 20.1 XEmacs Lucid (beta10)
Reply-To: derrell@vis-av.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII

>>>>> "  Tor" == Tor Arntsen <tor@spacetec.no> writes:

  Tor> If the tarball (always) is the sum of a virgin 19.15 and all
  Tor> the patches, then I suggest that you make the release number
  Tor> from the number of patches -- e.g. 19.15.p12 would be 19.15 +
  Tor> the twelve patches available so far.

  Tor> Then you should also number the patches (as they appear on the
  Tor> web page), so that someone could still refer to 'my XEmacs
  Tor> which is 19.15 + patch 1 & 3'.  (although I think such reports
  Tor> could quickly become a nightmare anyway :-)

For added utility, the tarball (or anyone's semi-patched XEmacs) could
be named with a hex number used as a bit-mask reflecting the patches
which have been replied (patches numbered beginning at zero), with bit
0 indicating patch 0 applied, etc.  For example, 19.15.p0x05 has
patches 0 and 2.	*** :-) :-) :-) ***

Derrell

