Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!decwrl!usenet.coe.montana.edu!nate
From: nate@cs.montana.edu (Nate Williams)
Subject: Re: The patchkit
Message-ID: <1993Mar22.072620.19614@coe.montana.edu>
Sender: usenet@coe.montana.edu (USENET News System)
Organization: CS
References: <g89r4222.732307558@kudu> <1993Mar21.014401.2911@fcom.cc.utah.edu> <JKH.93Mar21025906@whisker.lotus.ie> <RANDY.93Mar21111347@sierra.uucp>
Date: Mon, 22 Mar 1993 07:26:20 GMT
Lines: 45
In article <RANDY.93Mar21111347@sierra.uucp> randy@sierra.UUCP (Randy Terbush) writes:
>
>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 disagree.
>
>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.
Put together a new release? There are a few folks who are in the process
of doing this right now, but we want to do it 'right', and in the process
of updating all of the older sources in the original distribution
Ex: groff 1.01 -> 1.07
elvis 1.5 -> 1.7
etc..
However, if you want to take the time to make a new distribution based
on the patchkit, go for it!!
>
>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. :-)
C'mon now, not quite a 80char screen. 40 chars. work fine. :-)
We hope to have a new patchkit mechanism working by the time the
NEW release is in shape, but the one I am thinking about is a ways
down the road.
Nate
--
osynw@terra.oscs.montana.edu | Still trying to find a good reason for
nate@cs.montana.edu | these 'computer' things. Personally,
work #: (406) 994-4836 | I don't think they'll catch on -
home #: (406) 586-0579 | Don Hammerstrom