Date: Sun, 20 Sep 2020 22:28:50 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Plans for git Message-ID: <6ae80681-f866-756e-d361-10e742d2dbf5@FreeBSD.org> In-Reply-To: <slrnrmerpg.1s57.naddy@lorvorc.mips.inka.de> References: <CAPyFy2CTTecRJDnXNvF%2BM2%2BaLWJpA%2BEdG43ZeU3qwsCruecoFA@mail.gmail.com> <20200902045939.GA15897@eureka.lemis.com> <20200902060117.GG53210@home.opsec.eu> <20200902063136.GA47543@troutmask.apl.washington.edu> <CAPyFy2ANWEiA2ndE6qr_kY=sPuY%2BeaAZg=apWo0OZPVC7pkwkg@mail.gmail.com> <20200902164706.GA49777@troutmask.apl.washington.edu> <CANCZdfp8b78yNB8S2j1xHUKEz5iGNvdBGnw774_sXXtN9ucrSw@mail.gmail.com> <5c89b4d27281f5dfffc3252a90013b0ac6c763d7.camel@freebsd.org> <5c832482-b2bc-47e4-8762-8f5a886d5f11@www.fastmail.com> <e0b8e48e2942c019e05bdc21a6502379235f9073.camel@freebsd.org> <68585ca4-5ca4-40d3-b2f4-67ff3b35b6ae@www.fastmail.com> <0be2ae57d1c58e2091f4cc4484731df0@bsdforge.com> <967D73EA-880E-413D-B748-62A406C46524@FreeBSD.org> <9f89dc553e7d7b0884c2862329bdfeae@bsdforge.com> <CANCZdfqoFC9vD7ue=7FfYbaxYDivFxRX45DQNVRuidj%2BDvq_2A@mail.gmail.com> <CACpH0Mefr48tKfb-L-wiEPCCNMP31NumBrxJ%2B5eb02AmUt=hKw@mail.gmail.com> <slrnrmerpg.1s57.naddy@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Just my +100500 to this. On 20/09/2020 18:03, Christian Weisgerber wrote: > On 2020-09-19, Zaphod Beeblebrox <zbeeble@gmail.com> wrote: > >> Hrm. Maybe what I hear others saying, tho, and not entirely being replied >> to is just a nice concise document of the why. What I hear you saying is >> that GIT has momentum and that it's popular... (and I accept that --- it is >> evidently true), but then I hear handwaving about features, but no list of >> features that are a clear win/loose. > > How about the very basics (that Warner appears to have lost sight > of)? > > Git is a distributed version control system. You clone a repository > and apart from pulling and pushing changes to another repository, > all your work happens with the local repository. Subversion has a > central repository and needs to talk to the server all the time. > Laptop on a plane? No change of workflow with Git. > > And since it's your repository, you can cheaply create your own > branches, where you can commit your work and have a versioned history > of it instead of just a flat diff. I can't overstate the value of > that. Whether you work on something that will be pushed back > upstream or just your private changes, it has a full commit history. > You can easily revert commits, you can upstream it one by one, you > can upstream it with history. > > When FreeBSD switched from CVS to SVN, there was hope or promise > of lightweight branches, but that never materialized. Developers > still can't have private branches in the FreeBSD repository. For > a while, a lot of development happened in a Perforce repository--a > commerical version control system, whose company had donated a > license--which offered this feature. Nowadays, everybody who does > any but the most trivial development does so in a private Git > repository anyway. It only makes sense to interface this directly > with the FreeBSD repository instead of going through a SVN<>Git > media break. > >> Certainly the only clear things a quick search turns up that seem relevant >> is that GIT is GPL2.0 and SVN is Apache2.0. This was enough for LLVM vs >> GCC and the repository is a core function, but I suppose not a necessary >> function for forked projects that can't abide, so... > > There is a bit of historical precedent: The original BSD work at > Berkeley was kept in a SCCS repository, a proprietary version control > system at the time. > > And of course the fact that significant FreeBSD development has > effectively happened in Perforce, then in Git for a long time and > is just merged back into the Subversion repository. To put it > bluntly, the people doing the work have voted with their feet years > ago. > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ae80681-f866-756e-d361-10e742d2dbf5>