Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!newsfeed.direct.ca!hunter.premier.net!news-res.gsl.net!news.gsl.net!news.mathworks.com!newsfeed.internetmci.com!newsxfer2.itd.umich.edu!agate!theos.com!deraadt From: deraadt@theos.com (Theo de Raadt) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: List of OpenBSD changes Date: 13 Aug 1996 07:34:02 GMT Organization: Theo Ports Kernels For Fun And Profit, Inc. Lines: 51 Message-ID: <DERAADT.96Aug13013402@zeus.theos.com> References: <DERAADT.96Aug8144209@zeus.theos.com> <4ufqap$44i@jan.et.byu.edu> <v6lofo6lju.fsf@kechara.flame.org> <4uljtk$jb0@redstone.interpath.net> <DERAADT.96Aug11183115@zeus.theos.com> <v63f1r3im1.fsf@kechara.flame.org> NNTP-Posting-Host: zeus.theos.com In-reply-to: Michael Graff's message of 13 Aug 1996 02:26:13 -0400 In article <v63f1r3im1.fsf@kechara.flame.org> Michael Graff <explorer@flame.org> writes: deraadt@theos.com (Theo de Raadt) writes: > Let me chat a bit more about why CVS access is important: when looking > at a changed file, knowing WHY a change was made is often incredibly > important. That's what the cvs log message is for, but also it is > very important to look at the diffs for any SINGLE change all by > itself. NetBSD does not make their sources available in this form > which is a royal pain in the F*@Q#($ ass. I won't talk about what it > takes to track NetBSD changes, except that it is roughly 10x as much > effort (and, that may be a reason why noone in FreeBSD has gone > through the effort of looking at many NetBSD changes). Yea, here we find out the important piece of info that Theo has a dog. Aren't these things wonderful? Watch out, the sarcasm is dripping... I have one more thing to point out: You sent mail asking for a CommonBSD effort, but only 2 days later you are being insulting and derogatory towards the very people who are the closest towards merging the *BSD code into one CommonBSD, *AND* making it available so that YOU can merge it back into the source tree you work on?! I think it's clear that you missed the entire point of my article!!! You came into the newsgroup talking about a "CommonBSD" idea, but you are part of a group that does not make the changes to their source tree available, something which would be critical towards FOSTERING greater cooperation! You're talking about greater cooperation, but every step along the way the project you work with does - mailing list censorship - closed development (for whatever reason, about 3 months of changes in NetBSD are not available to the world) - restrictive agreements for developers (want more details?) - lies to members of the community about OpenBSD's and my past - restricts interested and skilled people from working on the source Get a grip, Michael -- the project you are working on is the *biggest* reason why a CommonBSD will not exist! You're just mad because I talked about the fact that the NetBSD source tree is polluted with illegal source code from during the BSDi/UCB/AT&T lawsuit. -- This space not left unintentionally unblank. deraadt@theos.com