Date: Wed, 18 Aug 2004 11:24:11 -0400 From: Aniruddha Bohra <bohra@cs.rutgers.edu> To: drhodus@machdep.com Cc: freebsd-current@freebsd.org Subject: Re: Public Access to Perforce? Message-ID: <4123749B.2090101@cs.rutgers.edu> In-Reply-To: <fe77c96b0408180819903cb74@mail.gmail.com> References: <200408160104.03708.chris@behanna.org> <fe77c96b04081807281c76200@mail.gmail.com> <200408181611.45299.dfr@nlsystems.com> <fe77c96b0408180819903cb74@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Could this please be moved to -chat or something. Current has too much traffic as it is :( Thanks Aniruddha David Rhodus wrote: >On Wed, 18 Aug 2004 16:11:44 +0100, Doug Rabson <dfr@nlsystems.com> wrote: > > >>On Wednesday 18 August 2004 15:28, David Rhodus wrote: >> >> >>>On Wed, 18 Aug 2004 17:57:19 +0400, Roman Kurakin <rik@cronyx.ru> >>> >>> >>wrote: >> >> >>>>I fully agree with you. But this not affect "open source"ness. >>>>I'd rather call it open development. >>>> >>>>rik >>>> >>>> >>>Yes, it does when the public doesn't have direct access to the >>>development work going on. Thats what started this thread in the >>>first place. >>> >>> >>This is ludicrous. You don't have access to my private source trees on >>my private machines where I test and develop software before committing >>it to CVS. How does that change the fact that when I commit that >>software it has a standard two clause BSD open source license. >> >> > >Well that is fine if that is the method in which you are using the >perforce system. But when overly large commits hit the cvs tree from >perforce which should have came with incremental changes so there >could be more detail public scrutiny, etc.. there is a problem. > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4123749B.2090101>