Date: Mon, 5 Dec 2005 15:28:51 +0000 From: RW <list-freebsd-2004@morbius.sent.com> To: freebsd-questions@freebsd.org Subject: Re: how to track 6.0 increments ? Message-ID: <200512051528.53138.list-freebsd-2004@morbius.sent.com> In-Reply-To: <200512051056.33305.ashley.moran@codeweavers.net> References: <43932546.4090904@redstarling.com> <200512051056.33305.ashley.moran@codeweavers.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 05 December 2005 10:56, Ashley Moran wrote: > On Sunday 04 December 2005 17:20, ke.han wrote: > > I don't want to follow current or stable (I don't think). =A0I just want > > security fixes and other changes that might be termed 6.01 if there were > > such a thing. > > I've always wondered this. Is there a reason why the FreeBSD team put > security updates into a branch rather than a 6_0_x release tag? If you are asking why they don't use a different tag for each point release= ,=20 then I think the answer is that it would require you to know precisely what= =20 the latest release is and edit the cvsup file each time. With RELENG_6_0 yo= u=20 get the latest point release automatically. Incidently in 6.0.x, x is not the point release number, it's a number that'= s=20 only rarely used. The 5.2 release had some substantial fixes, and the FreeB= SD=20 version was bumped up to 5.2.1, though the tag was still RELENG_5_2.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512051528.53138.list-freebsd-2004>