Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!mcsun!ieunet!dec4ie.ieunet.ie!jkh From: jkh@whisker.lotus.ie (Jordan K. Hubbard) Subject: Re: The patchkit (was Re: Excessive Interrupt Latencies) In-Reply-To: terry@cs.weber.edu's message of Sun, 21 Mar 93 01: 44:01 GMT Message-ID: <JKH.93Mar21025906@whisker.lotus.ie> Sender: usenet@ieunet.ie (USENET News System) Nntp-Posting-Host: whisker.lotus.ie Organization: Lotus Development Ireland References: <g89r4222.732307558@kudu> <C409MC.n1D@agora.rain.com> <1obts0$doq@hal.gnu.ai.mit.edu> <1993Mar21.014401.2911@fcom.cc.utah.edu> Date: Sun, 21 Mar 1993 02:59:06 GMT Lines: 31 [ Terry outlines a number of very good reasons why the patchkit is the way it is today ] After reading Terry's article, I realized that my somewhat off-the-cuff answer to Charles's original memo, in which I essentially say "I agree that the existing mechanism is inadequate, let's nuke it." may be very misleading to anyone who thinks that I intend to dump all aspects of the system and potentially introduce back some of the problems that Terry describes as being solved by the current patchkit. If so, I'm sorry for the misunderstanding. What I have in mind does not do away with the central coordination of patches, or even the unique stamping of patch numbers onto files (though whether or not the version numbers exist in exactly the same way is debatable), it has more to do with how they're applied, archived and sources are built from them. I'm not ready to publically go over the system I have in mind just yet, at 2:53 in the morning would be a poor time to try and describe it coherently even if I was, but my intended scheme essentially involves using CVS trees for the source and a lot more intelligence in the code handling automated application of patches. That's all I'm going to say for now - my last conscious braincell just fell asleep.. Jordan -- Jordan Hubbard Lotus Development Ireland jkh@whisker.lotus.ie 386bsd Patchkit Coordinator All-around nice dude. I do not speak for Lotus as that's not in my job description.