Date: Sun, 20 Sep 2020 16:34:06 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Christian Weisgerber <naddy@mips.inka.de>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Plans for git Message-ID: <CAJ-VmonarT5mN3DEygevatGn=zuJhMMAUtW1RBA3jbJHFC50fA@mail.gmail.com> In-Reply-To: <YTBPR01MB3966DE2569798A263AEB301CDD3D0@YTBPR01MB3966.CANPRD01.PROD.OUTLOOK.COM> 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> <YTBPR01MB3966DE2569798A263AEB301CDD3D0@YTBPR01MB3966.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Sep 2020 at 15:37, Rick Macklem <rmacklem@uoguelph.ca> wrote: > 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. > Well, I (mostly lurk) on the linux-nfs@vger.kernels.org mailing list, > where the Linux NFS work gets done. > What I see is the following, when someone has an enhancement/change > for the Linux NFS code. > Do I see one diff with all the changes in it...No. > I see anywhere from a few to over 50 email messages, each with > one little piece of the pie, out of git. > > I have no idea how they review this stuff. > It's done in patchwork.kernel.org. This takes the contents of very specifically correctly formatted git-email contents and wraps up the series as something that can be assigned to patchwork users for review/feedback. All of it goes in and out of email. It's basically using the public Linux email lists as part discussion and part RPC between everyones' git repositories. I think this stuff predates github, where there's a much nicer web flow for doing stuff like this. The linux model works great in a world where you're /truely/ decentralised. I bet that 99% of git users use some web frontend that's integrated into CI and patch review. HTH, -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonarT5mN3DEygevatGn=zuJhMMAUtW1RBA3jbJHFC50fA>