From owner-freebsd-current Tue Jun 6 15:12:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA17552 for current-outgoing; Tue, 6 Jun 1995 15:12:47 -0700 Received: from reinfra.regent.e-technik.tu-muenchen.de (root@reinfra.regent.e-technik.tu-muenchen.de [129.187.230.226]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA17532 for ; Tue, 6 Jun 1995 15:12:44 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by reinfra.regent.e-technik.tu-muenchen.de with SMTP id <51625>; Wed, 7 Jun 1995 00:12:06 +0200 Received: from localhost (localhost [127.0.0.1]) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) with SMTP id KAA08081; Tue, 6 Jun 1995 10:48:14 +0200 Message-Id: <199506060848.KAA08081@vector.eikon.e-technik.tu-muenchen.de> X-Authentication-Warning: vector.eikon.e-technik.tu-muenchen.de: Host localhost didn't use HELO protocol To: Nate Williams cc: "Rodney W. Grimes" , FreeBSD-current@FreeBSD.ORG (FreeBSD current) Subject: Re: sup is fetching whole src tree In-reply-to: Your message of "Sat, 03 Jun 1995 21:30:03 +0200." <199506031930.NAA19004@trout.sri.MT.net> Date: Tue, 6 Jun 1995 10:48:11 +0200 From: Julian Howard Stacey Sender: current-owner@FreeBSD.ORG Precedence: bulk Nate wrote: > The CVS 1.4-FAQ is now in our source tree in the cvs src directory. Thanks, I see src/gnu/usr.bin/cvs/FAQ: Archive-name: cvs-faq $Revision: 1.1.1.1 $ <<== Include this in your comments $Date: 1995/03/31 07:42:45 $ ftp.think.com/pub/cvs/FAQ-2.3 is the same except a diff shows: $Revision: 2.3 $ <<== Include this in your comments $Date: 1993/08/13 18:00:10 $ It seems FreeBSD CVS zapped the original Revision ? At least src/gnu/usr.bin/cvs/README has an unmangled Rev. No. in it: CVS Kit, Version 1.4 Alpha Suggestion for CVS on FreeBSD : Perhaps on freefall CVS initial commit we (or cvs ?) should prepend a FreeBSD CVS stamp, & then prevent CVS from mangling second and subsequent revision strings We would then have a src tree (rather than just a FreeBSD CVS tree), where - users could identify file versions without ftp'ing (or tar xv'ing etc) to check & compare. - subsequent embedded version strings would not get mangled (as Rod diagnosed was happening for instance on a (since fixed) version of ports/comms/hylafax/patches/patch-aa) Years ago I used SCCS something like this (I recall), - First line showed our company's internal SCCS string. - Next line was sometimes/often blank I seem to recall, - Next line was the unchanged Rev. No. (SCCS or whatever else) of whoever our software source was. Would this method be attractive to FreeBSD ? Julian S