Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!elroy.jpl.nasa.gov!ames!decwrl!netcomsv!dsndata!sierra!randy From: randy@sierra.UUCP (Randy Terbush) Subject: Re: The patchkit (was Re: Excessive Interrupt Latencies) Organization: Advanced System Design In-Reply-To: jkh@whisker.lotus.ie's message of Sun, 21 Mar 1993 02:59:06 GMT References: <g89r4222.732307558@kudu> <C409MC.n1D@agora.rain.com> <1obts0$doq@hal.gnu.ai.mit.edu> <1993Mar21.014401.2911@fcom.cc.utah.edu> <JKH.93Mar21025906@whisker.lotus.ie> Message-ID: <RANDY.93Mar21111347@sierra.UUCP> Sender: randy@sierra (Randy Terbush) Date: Sun, 21 Mar 1993 17:13:30 GMT Lines: 25 My 2 cents.... It is nearly impossible to maintain a patch system on a source tree the size of 386bsd when patchlevels are in excess of 100! I feel it would take less time to put together a new source release at patchlevel 0 (386bsd-0.2.0 ??) than to argue about the lackings of the current patch system. I know that 386bsd-0.2.0 conflicts with Bill Jolitz's current project, but by the sound of some of the changes being worked on, it may merit it's own ALPHA series. We should be working towards a reasonably stable 386bsd-1.0.0 at a faster rate than the current numbering scheme allows. After all, the numbers should give some indication of relative depenability. This SHOULD coincide with the release of patchkit-0.2.0 to eliminate some confusion about "What patchkit should I use??" questions. This would allow the patchkit revisions to be tracked in a way that doesn't require a NL to display the filename in an 80char screen. :-) -- Randy Terbush INET: randyt@cse.unl.edu UUCP: netcomsv!dsndata!randyt