At Tue, 9 Dec 2025 16:52:32 -0500, Andrew Cagney <andrew.cagney%gmail.com@localhost> wrote: Subject: Re: irt: Re: Core statement on version control systems > > On Wed, 3 Dec 2025 at 17:55, Greg A. Woods <woods%planix.ca@localhost> wrote: > > > > Again, thanks very much for writing up your thoughts! > > > > At Sat, 29 Nov 2025 23:18:04 +0000, David Holland <dholland-tech%netbsd.org@localhost> wrote: > > Subject: Re: irt: Re: Core statement on version control systems > > > > > > Pull requests are, though, a terrible vehicle for doing real work: > > > > Perhaps the guides written for the FreeBSD conversion to git will help > > offer a view that can simplify some things. > > > > https://docs.freebsd.org/en/articles/committers-guide/ > > > > It's obviously not simple though. > > All I can see are trees, am I in a forest? Yeah, I do think they have a bit of SVN baggage! > For instance: > > > Then you should have separated fetch and push URLs as the most efficient setup: > > they use a public readonly https endpoint when pulling, but then > git+authentication when pushing; but why? > The comment hints at performance. But I wonder if it is because it > lets one pull down updates without needing to go through > authentication. I'm not so sure this bit is about performance per se, but rather about the load on the back-end servers. If everyone fetches from a dedicated "fetch" server then the push server doesn't have to suffer the load of any fetch requests. > There must be a big picture work flow somewhere, I'm just not seeing it. Yeah, that committers-guide isn't easy to follow. I think it is all in there though, in spaghetti fashion -- it just needs a good summary to be written. I think the basic part is most developers will follow the normal "everyone commits/merges to the trunk". Release engineers follow the MFC (merge-from-current) procedures. There is also the guide Warner wrote about dealing with pull requests from outsiders. -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpGedgtnaHlq.pgp
Description: OpenPGP Digital Signature