Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!hookup!usenet.eel.ufl.edu!piaget.moe.ac.sg!raffles.technet.sg!einstein.technet.sg!jseng From: jseng@technet.sg (James Seng) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Patches for FreeBSD Date: 17 Aug 1995 05:49:42 GMT Organization: Technet, Singapore Lines: 20 Message-ID: <40ul9m$a6@raffles.technet.sg> References: <40ju7f$qk7@raffles.technet.sg> <40k13j$g7@agate.berkeley.edu> <40kd47$kqj@fu-berlin.de> <40kvig$c5i@agate.berkeley.edu> NNTP-Posting-Host: jseng@einstein.technet.sg X-Newsreader: TIN [version 1.2 PL2] Jordan K. Hubbard (jkh@violet.berkeley.edu) wrote: : I never said that such patches might not be useful, but actually providing : them for each stage of "bug fixing" and within a provided framework for : applying, reversing and previewing such patches is a significant amount : of work, and we're rather overextended as it is. Thank for the information Jordon. I understand the time is needed to produce the patch. Just an idea, if there is 100 people using FreeBSD, wont it be more efficient if one people produce a patch file then 100 people each doing it for himself? Sadly, I dont have much time on hand myself or else i would volunteer myself for the one-man-task. Another possible solution i can see is to do patches like how port is done. Create a /usr/src/patch directory, a bsd.patch.mk file etc.. In this manner, patches can be done by various people and it will be distributed thru ftpsite the same why port is done. -James Seng