From owner-freebsd-stable  Wed Oct  8 18:18:06 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA28278
          for stable-outgoing; Wed, 8 Oct 1997 18:18:06 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: (from jmb@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA28265;
          Wed, 8 Oct 1997 18:18:00 -0700 (PDT)
          (envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199710090118.SAA28265@hub.freebsd.org>
Subject: Re: CVSup release identity
To: nate@mt.sri.com (Nate Williams)
Date: Wed, 8 Oct 1997 18:17:59 -0700 (PDT)
Cc: Hetzels@aol.com, nate@mt.sri.com, stable@freebsd.org
In-Reply-To: <199710081903.NAA11742@rocky.mt.sri.com> from "Nate Williams" at Oct 8, 97 01:03:32 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Nate Williams wrote:
> 
> > >  I suggest spending less time arguing, and more time coming up with a
> > >  *solution*, and not a proposed solution.  Changes to the tree,
> > >  newvers.sh, etc....
> > >  
> > We're trying to come up with the solution but it basically, involves three
> > areas.
> > 1. Creation of a .timestamp file added to the source tree.
> 
> Sure, the only thing that's disagreed upon is the format of the
> timestamp, and how often it's built.  *THIS* is the crux of the matter,
> and if you can come up with *something*, then the rest is politics.

	we need timestamps to track changes to the source.
	timestamp file is generated as a result of cvs commit.
	each commit changes the timestamp file.
	if 4 days go by without a commit ;)
	the timestamp file does not change

	timestamp is then incorporated into uname
	(hhmmm....every commit means a kernel recompile ;<)
	extend uname to write the timestamp into the kernel ala hostname.
	add this to /etc/rc.....???

	doesnt matter how you get your bits, cvs ctm carrier pigeon.
jmb