cvsup usable UTC date for tracking -stable
i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? for example, i want to sync src to 4.5-rc2 but not current -stable. what date will it be, then, for 4.5-rc2? i read RELNOTES and README at... ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.5-RC2/ ...couldn't find anything (or, i missed). - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvsup usable UTC date for tracking -stable
On Sun, 20 Jan 2002 at 03:21:00 -0500, parv wrote: i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? for example, i want to sync src to 4.5-rc2 but not current -stable. what date will it be, then, for 4.5-rc2? i read RELNOTES and README at... ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.5-RC2/ ...couldn't find anything (or, i missed). I'm not sure what you're talking about here. The current -STABLE branch *is* 4.5-RC2. - jim -- jim mock [EMAIL PROTECTED] http://soupnazi.org/ | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvsup usable UTC date for tracking -stable
At 12:42 AM 1/20/2002 -0800, Jim Mock wrote: On Sun, 20 Jan 2002 at 03:21:00 -0500, parv wrote: i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? for example, i want to sync src to 4.5-rc2 but not current -stable. what date will it be, then, for 4.5-rc2? i read RELNOTES and README at... ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.5-RC2/ ...couldn't find anything (or, i missed). I'm not sure what you're talking about here. The current -STABLE branch *is* 4.5-RC2. I think the original poster was asking how to use cvsup to sync source tree to the exact cut of a rcX.iso. aka how to reproduce exactly the source that was used to generate an official RC. It's going to be something like src-all date=2002.01.xx.xx.xx.xx in the supfile. That'll allow testing to happen, without needing to pull an entire .iso file. Of course, 'cvsup - make world' is not the same as 'insert cd, install from scratch' - jim -- jim mock [EMAIL PROTECTED] http://soupnazi.org/ | [EMAIL PROTECTED] --chris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvsup usable UTC date for tracking -stable
in message [EMAIL PROTECTED], wrote Christopher Schulte thusly... At 12:42 AM 1/20/2002 -0800, Jim Mock wrote: On Sun, 20 Jan 2002 at 03:21:00 -0500, parv wrote: i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? ... I'm not sure what you're talking about here. The current -STABLE branch *is* 4.5-RC2. jim, i know. but after release of the -rc2 iso image, -stable is more than just -rc2. I think the original poster was asking how to use cvsup to sync source tree to the exact cut of a rcX.iso. aka how to reproduce exactly the source that was used to generate an official RC. yes, that is exactly what i am seeking: how to find the date of sources from which the iso image is built. It's going to be something like src-all date=2002.01.xx.xx.xx.xx in the supfile. That'll allow testing to happen, without needing to pull an entire .iso file. Of course, 'cvsup - make world' is not the same as 'insert cd, install from scratch' i guess, it's not. then again, i am doing it for my own peace of mind, not necessarily actively testing the -rc2. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvsup usable UTC date for tracking -stable
On Sun, Jan 20, 2002 at 03:21:00AM -0500, parv wrote: i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? for example, i want to sync src to 4.5-rc2 but not current -stable. what date will it be, then, for 4.5-rc2? We don't lay down tags for the release candidates, so there is no easy way to get the EXACT bits that we used for RC2. If you really want to try, then you can just use cvsup to pull down the sources based on a given time. The build was started about 8 hours before my announcement to this list. In general, it would be just as good if not better if you could just sync to the newest RELENG_4 (-STABLE/-RC) code, since any additional commits between RC2 and now need testing. Hope that helps. - Murray msg40306/pgp0.pgp Description: PGP signature
