Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@erewhon.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.development
Subject: Re: [The Great Patch-kit Debate] Bugs, Annomolies, Patches, Hacks, Fixes, Rewrites & Experimental
Date: 8 Apr 93 04:26:32
Organization: Kernel Hackers 'r' Us
Lines: 34
Message-ID: <CGD.93Apr8042632@erewhon.CS.Berkeley.EDU>
References: <jmonroyC55tAy.462@netcom.com>
NNTP-Posting-Host: erewhon.cs.berkeley.edu
In-reply-to: jmonroy@netcom.com's message of Thu, 8 Apr 1993 10:04:09 GMT
In article <jmonroyC55tAy.462@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes:
> [ ... ]
> PATCH-KIT - Released weekly without regard for consequence
> [ ... ]
> HACK-KIT - The same as above. This is just different code.
> [ ... ]
i think the thing to emphasize here is "Released weekly".
as some of you are, i'm sure, aware, i'm one of the people involved
in trying to get together an interim release.
basically, the goal will be an initial source- and binary- release,
to get everybody "in sync" with my environment. then, weekly,
complete diffs from the previous week will be automatically
(as in: with cron) posted to the net. subsequent "full releases"
will happen, but, for a while, only the source release
will be updated automatically.
i think that *regularity* of releases of fixes and bug lists should be
the "prime directive", if only because it lets people know what
is going on. I think that this regularity is one major
area in which linux currently has an advantage over 386bsd.
chris
whose come to love CVS... it makes it pretty easy to manage
5 or 7 hackers, beating on a 50+M source tree...
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass