From owner-freebsd-stable Thu Nov 20 19:33:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06907 for stable-outgoing; Thu, 20 Nov 1997 19:33:15 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (s204m97.whistle.com [207.76.204.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA06902 for ; Thu, 20 Nov 1997 19:33:10 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA00434; Fri, 21 Nov 1997 13:57:10 +1030 (CST) Message-Id: <199711210327.NAA00434@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: chad@dcfinc.com cc: freebsd-stable@freebsd.org Subject: Re: Version Resolution? In-reply-to: Your message of "Thu, 20 Nov 1997 17:36:26 PDT." <199711210036.RAA04422@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Nov 1997 13:57:10 +1030 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > No, think a bit larger. Make newvers.sh have a keyword (like %%date%%) > > > that a sed script could use to replace the "counter" as a part of a > > > commit. Only do the RCS/CVS drill on newvers.sh if something =other > > > than= the date string changes. > > > > And where does this counter number come from? We're back at the same > > place we started. > > Date/time at the moment of the commit. Format it how you like. Only you don't want it in newvers.sh; it needs to be generated at checkout/update time, and coming up with a mixed "normal/special" object would be a great deal harder than just a "special" object. Nate's right, it's not easy. I've just given myself a headache looking at the CVS sources. 8) mike