From owner-cvs-all Thu Feb 11 09:07:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13194 for cvs-all-outgoing; Thu, 11 Feb 1999 09:07:06 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13185; Thu, 11 Feb 1999 09:06:59 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA07552; Thu, 11 Feb 1999 09:06:58 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA55863; Thu, 11 Feb 1999 09:06:58 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 11 Feb 1999 09:06:58 -0800 (PST) Message-Id: <199902111706.JAA55863@vashon.polstra.com> To: eivind@FreeBSD.ORG Subject: Re: cvs commit: src/contrib/gcc/config/i386 freebsd.h src/sys/sys param.h In-Reply-To: <19990211114037.X96008@bitbox.follo.net> References: <199902110929.UAA19899@godzilla.zeta.org.au> <19990211020516.B29538@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Cc: committers@FreeBSD.ORG Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk In article <19990211114037.X96008@bitbox.follo.net>, Eivind Eklund wrote: > On Thu, Feb 11, 1999 at 02:05:16AM -0800, David O'Brien wrote: > > > > contrib/gcc/config/i386 freebsd.h > > > > Log: > > > > Set __FreeBSD_cc_version for 3.1 > > > > > > This is bogus. FreeBSD's version of cc didn't change. > > > > According to rev 1.21, "change the numbering scheme of > > __FreeBSD_cc_version. Its form is now like __FreeBSD_version, with the > > FreeBSD revision in the top digits." > > I don't think we should bounce this unless it is necessary (ie, change > it when there are changes in cc, and at that point include the FreeBSD > revision in the top digits). The only benefit I can see in bouncing > it otherwise is if somebody forget to bounce it when they do changes. The main thing as far as I'm concerned is that we have to be able to track changes independently on different branches that exist at the same time, e.g., RELENG_3 and -current. That was the rationale for putting the FreeBSD release number in the top digits. For example, it's not inconceivable that some day we'll add a new feature only in the -stable branch, and a different new feature in -current. A single monotonically-increasing __FreeBSD_version shared by all the branches wouldn't handle that. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message