Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Aug 2001 19:37:36 +0300
From:      Ruslan Ermilov <ru@FreeBSD.org>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        freebsd-doc@FreeBSD.org, bug-followup@FreeBSD.org
Subject:   Re: docs/29767: incorrect description of 'standart-supfile'
Message-ID:  <20010816193735.O73183@sunbay.com>
In-Reply-To: <XFMail.010816075907.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Thu, Aug 16, 2001 at 07:59:07AM -0700
References:  <200108160800.f7G803398475@freefall.freebsd.org> <XFMail.010816075907.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 16, 2001 at 07:59:07AM -0700, John Baldwin wrote:
> 
> On 16-Aug-01 Ruslan Ermilov wrote:
> > The following reply was made to PR docs/29767; it has been noted by GNATS.
> > 
> > From: Ruslan Ermilov <ru@FreeBSD.ORG>
> > To: Olexandr Kunytsa <kunia@x-telecom.net>
> > Cc: FreeBSD-gnats-submit@FreeBSD.ORG
> > Subject: Re: docs/29767: incorrect description of 'standart-supfile'
> > Date: Thu, 16 Aug 2001 10:58:13 +0300
> > 
> >  On Thu, Aug 16, 2001 at 10:43:03AM +0300, Olexandr Kunytsa wrote:
> >  > 
> >  > standard-supfile in -stable now gets you the -stable sources, but it
> >  > is pointed inside the file that it contains "CVSup collections" for
> >  > current-sources.
> >  > 
> >  And also in README.  I think that either
> >  
> >       standard-supfile should be deleted from -STABLE
> >  
> >  *OR*
> >       standard-supfile should be (repo)moved to current-supfile
> >       in -CURRENT, and MFC'ed to -STABLE.  With corrections to
> >       README.
> 
> Erm, in the original discussion about this, there was the point that
> 'standard-supfile' was supposed to follow whatever current branch you were on
> at the time.  Thus, on 4.x, standard-supfile follows RELENG_4, on 4.3, it
> follows RELENG_4_3, and on -current it follows HEAD.
> 
But it doesn't, in fact, follows 4.3 on RELENG_4_3, it's still set to
RELENG_4 there.  Nor it is to fetch RELENG_4_3 in RELENG_4_3_0_RELEASE.
And `standard' comes yet from `crypto' times, it assumes `non-standard'.

How about this?  For X.Y release, that would be:

release-supfile		RELENG_X_Y_RELEASE
bugfix-supfile		RELENG_X_Y
stable-supfile		RELENG_X
current-supfile		.

For -CURRENT, only stable-supfile and current-supfile make sense probably.


Cheers,
-- 
Ruslan Ermilov		Oracle Developer/DBA,
ru@sunbay.com		Sunbay Software AG,
ru@FreeBSD.org		FreeBSD committer,
+380.652.512.251	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010816193735.O73183>