On Tue, Oct 29, 2024 at 04:57:48PM -0600, Bob Proulx wrote: > Ian Kelling wrote: > > Ineiev writes: > > > Yes; our Git server already can't cope with its current load, > > > https://savannah.gnu.org/support/?110712 ... > The git server is not overloaded at this time. It is handling the > steady state of normal usage acceptably well. ... > I am reviewing the system while typing this. Looks good. ...
Then you could check if any issues in that support request persist and close it, or at least comment on what problems are left. > But yes, git introduced the concept of full history clones and too > much full history cloning has caused problems. I am sure it will > continue to cause problems. Unfortunately I am unaware of any way to > force the Right Thing to happen. It's an education issue. > > For the most part we have gotten the word out to use shallow clones. I would say, shallow pulls---not sure if I'm using correct words. the point isn't only to save the resources when initializing working copies. with CVS, one can update and commit single files without fetching their history and history of other files (to say nothing of their latest revisions). I wonder if git can update all files at once without getting their history and remain convenient enough.
signature.asc
Description: PGP signature
