Date: Mon, 6 Dec 2004 13:54:40 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Jose M Rodriguez <josemi@freebsd.jazztel.es>, freebsd-stable@freebsd.org Cc: Rob <spamrefuse@yahoo.com> Subject: Re: names of supfiles in /usr/share/examples/cvsup Message-ID: <p0620074dbdda5abd5b76@[128.113.24.47]> In-Reply-To: <200412061936.35851.freebsd@redesjm.local> References: <41B40C97.7000102@yahoo.com> <200412061936.35851.freebsd@redesjm.local>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:36 PM +0100 12/6/04, Jose M Rodriguez wrote: >El Lunes, 6 de Diciembre de 2004 08:39, Rob escribi=F3: >> Hi, >> >> For 5.3 in /usr/share/examples/cvsup, there's: >> >> stable-supfile : for FreeBSD-stable >> standard-supfile : for FreeBSD-current >> >> I find this naming rather confusing. Why "stable" refers to STABLE, >> but "standard" refers to CURRENT ? >> >> This causes unnecessary confusion. Why not the following name >> convention: >> >> release-supfile : for FreeBSD-RELEASE > >Better security-supfile. There is just one release, things like >RELENG_5_3 are security branchs, not release branchs. Let me add to the pain by noting that RELENG_5_3 is not a security branch (the way we used to have security branches). It is now called an "errata branch", and it may see some updates which are not for security issues. Not many, and only "really really safe" ones, but it is more than just security fixes... -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0620074dbdda5abd5b76>