Re: fork()
William Lahti <[email protected]> Sat, 7 Jan 2006 13:44:57 -0500
| Newsgroups | gmane.comp.graphics.y.devel |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_58166_29475969.1136659497007 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I do think a lot of people (myself included) were put off by the need to learn a totally new SCM system. I hear SVN is much more similiar to CVS (an= d thus easier for people who know CVS to learn). Yeah, I vote for SVN. On 1/7/06, Augie Fackler <[email protected]> wrote: > > The other nice thing about subversion is that it would allow those > who want/need to be distributed to be so through use of svk. I recall > arch getting in the way more than anything as well. > > On Jan 7, 2006, at 11:02 AM, James Harr wrote: > > > I vote subversion as well. > > > > - Subversion is, for a lot of users, a lot easier to learn. It has > > really well written documentation and provides several comparisons to > > CVS. arch only seemed to get in the way of people. It's really a great > > piece of software, but it seemed to disenchant a lot of people. > > - Y-windows is going to have little need for a distributed repository. > > There will be a few people working on it a lot (direct commit > > privileges) and possibly a lot of people doing tiny bugfixes, which > > can be made into patches and then submitted. Anyone who needs to do > > any branching/merging or moving of files will probably have direct > > commit access to the repository, so there is no need for arch's > > patches that handle changes to directories. > > - For what I've used subversion for it seems to fit the bill for the > > Y-Windows project. > > > > There's my two cents. > > > > -jh > > > > On 1/7/06, Harrison Caudill <[email protected]> wrote: > >> On 1/6/06, Kristian Mueller <[email protected]> wrote: > >> > >> <snip> > >> > >>> But I have to admit, that I have not tryed it in person - though > >>> I am > >>> planing to. > >> > >> Considering the number of people involved in this, and the magnitude > >> of our undertaking, I recommend we limit our experimentation to > >> graphics, not source control. > >> > >> I vote subversion. > >> > >> Harrison > >> > >> -- > >> Harrison Caudill BS BS | .^ www.hypersphere.org > >> Computer Science & Physics Graduate | | Me*Me=3D1 > >> Georgia Institute of Technology | v' I'm just a > >> normal guy > >> > > > > > > -- > > James Harr <[email protected]> > > > > > > ------=_Part_58166_29475969.1136659497007 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I do think a lot of people (myself included) were put off by the need to le= arn a totally new SCM system. I hear SVN is much more similiar to CVS (and = thus easier for people who know CVS to learn). Yeah, I vote for SVN.<br> <br><div><span class=3D"gmail_quote">On 1/7/06, <b class=3D"gmail_sendernam= e">Augie Fackler</b> <<a href=3D"mailto:[email protected]">durin@sbcgl= obal.net</a>> wrote:</span><blockquote class=3D"gmail_quote" style=3D"bo= rder-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding= -left: 1ex;"> The other nice thing about subversion is that it would allow those<br>who w= ant/need to be distributed to be so through use of svk. I recall<br>arch ge= tting in the way more than anything as well.<br><br>On Jan 7, 2006, at 11:0= 2 AM, James Harr wrote: <br><br>> I vote subversion as well.<br>><br>> - Subversion is, fo= r a lot of users, a lot easier to learn. It has<br>> really well written= documentation and provides several comparisons to<br>> CVS. arch only s= eemed to get in the way of people. It's really a great <br>> piece of software, but it seemed to disenchant a lot of people.<br= >> - Y-windows is going to have little need for a distributed repository= .<br>> There will be a few people working on it a lot (direct commit <br>> privileges) and possibly a lot of people doing tiny bugfixes, whic= h<br>> can be made into patches and then submitted. Anyone who needs to = do<br>> any branching/merging or moving of files will probably have dire= ct <br>> commit access to the repository, so there is no need for arch's<br= >> patches that handle changes to directories.<br>> - For what I've u= sed subversion for it seems to fit the bill for the<br>> Y-Windows proje= ct. <br>><br>> There's my two cents.<br>><br>> -jh<br>><br>> = On 1/7/06, Harrison Caudill <<a href=3D"mailto:Harrison.Caudill@hypersph= ere.org">[email protected]</a>> wrote:<br>>> On 1/6= /06, Kristian Mueller < <a href=3D"mailto:[email protected]">[email protected]</a>>= ; wrote:<br>>><br>>> <snip><br>>><br>>>> B= ut I have to admit, that I have not tryed it in person - though<br>>>= > I am <br>>>> planing to.<br>>><br>>> Considering the number= of people involved in this, and the magnitude<br>>> of our undertaki= ng, I recommend we limit our experimentation to<br>>> graphics, not s= ource control. <br>>><br>>> I vote subversion.<br>>><br>>> Harriso= n<br>>><br>>> --<br>>> Harrison Caudill BS BS = |&= nbsp; .^ <a href=3D"htt= p://www.hypersphere.org">www.hypersphere.org </a><br>>> Computer Science & Physics Graduate | = | Me*Me=3D1<br>>> Georgia Institute of Technology &n= bsp; | v' = I'm just a<br>>> normal guy<br>>><br>><br>><br>> --<br= >> James Harr < <a href=3D"mailto:[email protected]">[email protected]</a>><br>>= ;<br><br><br><br></blockquote></div><br> ------=_Part_58166_29475969.1136659497007--