Return to BSD News archive
Newsgroups: comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!virtech!dwex From: dwex@aib.com (David E. Wexelblat) Subject: Re: Status on discussed merge between NetBSD and FreeBSD Message-ID: <CGIB20.7xs@aib.com> Organization: AIB Software, Inc. References: <CGD.93Nov14100033@eden.cs.berkeley.edu> <CGHv40.BKF@kithrup.com> <CGD.93Nov14105344@eden.CS.Berkeley.EDU> Date: Mon, 15 Nov 1993 00:08:23 GMT Lines: 63 In article <CGD.93Nov14105344@eden.CS.Berkeley.EDU> cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes: >In article <CGHv40.BKF@kithrup.com> sef@kithrup.com (Sean Eric Fagan) writes: >>>Or perhaps some details from Jordan >>>as to why FreeBSD decided to make this announcement... >> >>I think you already know that. Or did you think that removing CVS access >>for only the freebsd folks was going to have no ramifications? > >If that was their reasoning, perhaps they should have made it public. >Ahh, Mr. Big (Mouth) is making himself spokesman for FreeBSD? Just curious - how old are you? Planning to reach puberty this decade, I hope. > >Also, i'd be more inclined to believe your argument if the chronology >were what you claimed. Jordan's note was posted to .announce at: >13 Nov 1993 22:31:38 -0800. CVS access on lamp for FreeBSD developers >not working on the NetBSD source tree at 22:40 (-0800, 13 November). >How do i know? well, i'm looking at the ctime of a file that i chmodded >when their access went away. You can't call it a response if it happens >before what it's responding to. "cause and effect; logic 101." > >Note that people working on FreeBSD who *are* working on NetBSD >did not have their access to NetBSD's CVS tree denied. Only those >who are doing no work on NetBSD cannot access our CVS tree. >Therefore, you can't claim that we're kicking people out of our >tree because they work with (or even mostly with) FreeBSD; that's >just not true. If they're not working on NetBSD, then they don't >have access; plain and simple. > Well, people, bizarre as this sounds, I think this posting proves Jesus Monroy right. Chris - you should step down as moderator. You are not only biased, you are vindictive. I suppose I can expect to have problems getting XFree86 stuff posted in the future now. Man, you make me sick. For that matter, I'm pretty much sick of ALL of this BSD-du-jour junk. You folks can't agree on ANYTHING, can you? Why is it that XFree86 has to support 3 different console driver APIs? And that there are still more around that aren't supported (I think)? There WAS a task force that was going to try to resolve all of this for us - to come up with a single common API for the console driver. But your bloody egos couldn't even accomplish that much - one subset of ioctl()s on one device. > > >chris >-- >chris g. demetriou cgd@cs.berkeley.edu > > smarter than your average clam. -- David Wexelblat <dwex@aib.com> (703) 430-9247 Fax: (703) 450-4560 AIB Software, Inc., 46030 Manekin Plaza, Suite 160, Dulles, VA 20166 Formerly Virtual Technologies, Inc. Mail regarding XFree86 should be sent to <xfree86@physics.su.oz.au> "Ooh, are you feelin' satisfied? Come on, let us give your mind a ride." -- Boston, "Feelin' Satisfied"