Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!yarrina.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!in2.uu.net!bloom-beacon.mit.edu!ai-lab!usenet From: miguel@sphinx.nuclecu.unam.mx (Miguel de Icaza) Newsgroups: comp.os.linux.advocacy,comp.unix.bsd.freebsd.misc,comp.unix.advocacy,comp.unix.misc Subject: Re: Linux vs FreeBSD Date: 04 Dec 1995 17:33:31 -0600 Organization: Universidad Nacional Autonoma de Mexico Lines: 31 Sender: miguel@sphinx.nuclecu.unam.mx Message-ID: <s8hgzgxv3o.fsf@sphinx.nuclecu.unam.mx> References: <489kuu$rbo@pelican.cs.ucla.edu> <49pb5g$di8@agate.berkeley.edu> <49s93l$a6@dyson.iquest.net> <DJ1B47.83F@kroete2.freinet.de> <DJ2I3J.6tp@nntpa.cb.att.com> NNTP-Posting-Host: hill.gnu.ai.mit.edu In-reply-to: dyson@inuxs.inh.att.com's message of Mon, 4 Dec 1995 15:09:19 GMT X-Newsreader: Gnus v5.0.1 Xref: euryale.cc.adfa.oz.au comp.os.linux.advocacy:29052 comp.unix.bsd.freebsd.misc:9739 comp.unix.advocacy:11675 comp.unix.misc:19796 > So, I would sure like to hear about the Linux CVS tree and > how concurrent development is handled. How does the Linux development > resolve differences given multiple developers making changes to the tree? Usually, there are people in charge of different parts of the Kernel and Linus gives them authority over that (ie, he just applies patches without doing much checking of them). The MIPS people have control over the MIPS part; the SPARC people over the SPARC dependant part; the network is handled by the network guy and so on. > At least it appears that FreeBSD has admitted to a long history of having > a concurrent version control system -- is there a secret one somewhere in > Linux, or is it just not open, and a single developer maintains the tree??? I don't think Linux developement tree is closed at all, you can get (as I said in a previous message) an almost updated look at what does the kernel look like with about 4-5 days of delay. If you want to touch some part of the kernel, Linus usually points you to the person or team in charge of that part and you discuss that with the appropiate team. Having CVS would be nice (Linux/SPARC works like this), but I really don't mind using any of the approachs for looking at kernel updates, and I'm really impressed by OpenBSD's anoncvs site. Miguel. -- miguel@roxanne.nuclecu.unam.mx The Midnight Commander: http://stekt.oulu.fi/~jtklehto/mc/