Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!rutgers!uwvax!oka.cs.wisc.edu!jcargill From: jcargill@oka.cs.wisc.edu (Jon Cargille) Newsgroups: comp.os.386bsd.development Subject: Re: interim release. Message-ID: <1993Jul19.142624.12887@cs.wisc.edu> Date: 19 Jul 93 14:26:24 GMT References: <JKH.93Jul17212255@whisker.lotus.ie> <CAEwsw.2xz@veda.is> Sender: news@cs.wisc.edu (The News) Organization: U of Wisconsin CS Dept Lines: 30 In article <CAEwsw.2xz@veda.is> adam@veda.is (Adam David) writes: > >Is it compatible with the patchkit or is this an isolated thing? [...] >What I would like to see (is this wishful thinking?) is that patchkit >0.2.5 would serve as a way of upgrading from patchkit 0.2.4 to the interim >version (386bsd 1.5 or whatever), or that the 2 paths if separate for awhile >will merge again fairly quickly, say with patchkit 0.2.6. There just seems >to be a bit too much unnecessary diversity if there are so many versions of >386bsd 0.1 around (patchkit, interim, netBSD). > >-- >adam@veda.is I strongly doubt that it will be possible to grab patchkit-0.2.5, and be upgraded to the "interim version". However, if you're concerned about there being "yet another branch" on the 386bsd tree, I don't think you need to be concerned. The "interim release" is put together by most of the patchkit folks. Instead, think of the "interim" release as a new baseline for future patchkits. (Though the patchkit mechanism will hopefully change for the better). Jon -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. Jon Cargille jcargill@cs.wisc.edu Want your .sig compressed? Reasonable rates and fast turnaround. Call today!