Date: Sat, 27 Sep 1997 20:39:46 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Greg Lehey <grog@lemis.com> Cc: Nate Williams <nate@mt.sri.com>, "Jordan K. Hubbard" <jkh@time.cdrom.com>, hackers@freebsd.org Subject: Re: How do I check out a snapshot? Message-ID: <199709280239.UAA28656@rocky.mt.sri.com> In-Reply-To: <19970928105411.00690@lemis.com> References: <199709272233.QAA27878@rocky.mt.sri.com> <Pine.BSF.3.96.970928063923.313J-100000@Journey2.mat.net> <199709272247.QAA28003@rocky.mt.sri.com> <19970928105411.00690@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I still don't see the problem. CVS already has the solution: the RE > selects a certain date for the snap, basically whatever he wants. Yeah, right. "OK, on Saturday, everything must work right, caue that's when I'm building the SNAP." *sarcasm on* How about it Jordan, seems reasonable and should work fine, right? *sarcasm off* > He waits for the time to pass, pulls a copy of the repository (though > this is not really necessary), and then checks out -current as of the > time he decided for the snap. And if it doesn't work, then what? He fixes bugs, and whiles he fixing them someone else is introducing new ones. The idea behind SNAPS is they're supposed to be fairly easy to produce, so going through the same gyrations as what is required for RELEASES shouldn't have to be done. If the world were a perfect place it would work fine, but it isn't. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709280239.UAA28656>