From owner-freebsd-stable Wed Oct 8 12:59:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10970 for stable-outgoing; Wed, 8 Oct 1997 12:59:48 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA10964 for ; Wed, 8 Oct 1997 12:59:43 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id NAA03737; Wed, 8 Oct 1997 13:59:41 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA12037; Wed, 8 Oct 1997 13:59:39 -0600 (MDT) Date: Wed, 8 Oct 1997 13:59:39 -0600 (MDT) Message-Id: <199710081959.NAA12037@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Hetzels@aol.com Cc: nate@mt.sri.com, stable@freebsd.org Subject: Re: CVSup release identity In-Reply-To: <971008155108_-1194179101@emout15.mail.aol.com> References: <971008155108_-1194179101@emout15.mail.aol.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > 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. > > This file is re-created at the Master Source Repository, every time someone > updates the source tree. Or, at a regular time. (But, I think that's also a political issue. I don't think we need that fined grained of control, and it might be a significant 'confusion' point trying to determine the *exact* point.) > NOTE: There would be a different timestamp file in each Branch (3.0, 2.2, > 2.1) that needs to be tracked. Good point. >>> How do we implement timestamp so that it updates the .timestamp file at >>> the Master Source Repository? > > That's the only real issue IMHO. The rest is politics, and can be > > argued about with no agreement until hell freezes over with no > > resolution. Give me *A* working solution, and then whoever can argue > > about making it a better solution. Something is almost always better > > than nothing, especially in this case. If you can come up with *a* good > > solution, and no-one can come up with an agreement on a 'better' > > solution, the good one will be 'good enough'. > > This is the one solution I don't know how to solve, the rest was easy. Right, hence my jumping in. Talk is cheap, real solutions are harder. > 1. What is the Master Source Repository using to track the source code? > (RCS?) CVS. > 2. How do you go about implementing a hook in to the source tracking code so > that it will automatically update the ".timestamp" file after each update to > the source tree. > > pseudo code: > > Check out ".timestamp" > > date "+%C%m%d%H%M" > ".timestamp" > > Check in ".timestamp" You've got the sources, go to it. :) (Hint, look at all the files in CVSROOT.) > 3. Would it update the timestamp file after each file is checked in or after > the person updating the source tree has finished? Don't know, what do you think? Seriously, these are the *technical* issues that need to be resolved, the rest is political. Come up with a solution to them and *THEN* you'll see some folks who have up to this point mostly ignored things interested. Until then you're just practicing your typing skills. Nate