Thanks!

To git@git.sr.ht:~sircmpwn/paste.sr.ht
   4cb7f21..0099792  master -> master

Thanks!

To git@git.sr.ht:~sircmpwn/lists.sr.ht
   d1c5f3a..e1ae776  master -> master

Thanks!

To git@git.sr.ht:~sircmpwn/sr.ht-docs
   30c96e4..db107d5  master -> master

Thanks!

To git@git.sr.ht:~sircmpwn/builds.sr.ht
   519c4d1..b4a1b40  master -> master

Will let this get picked up naturally through the rebuild cronjobs.

Can I also get a patch updating sr.ht-docs?

Got it.

To git@git.sr.ht:~sircmpwn/todo.sr.ht
   dc8988e..47ea6d9  master -> master

Thanks!

To git@git.sr.ht:~sircmpwn/todo.sr.ht
   dc8988e..47ea6d9  master -> master

Thanks!

To git@git.sr.ht:~sircmpwn/sr.ht-docs
   e474ec9..30c96e4  master -> master

https://git-scm.com/docs/git-config#Documentation/git-config.txt-uploadarchiveallowUnreachable

It's not super well documented.

On Tue Sep 3, 2024 at 9:17 PM CEST, Zack Weinberg wrote:
> It's not my present circumstance, but if you would like a reason why
> a self-service way to run an immediate "git gc --expire=now" would
> be useful _to you as a hosting service_, consider the situation
> where someone accidentally pushes something very large to the
> server.  Maybe they notice almost immediately and force-push
> a new commit without the blob, whatever it is, but it's still
> hogging disk space and possibly slowing down all operations on
> that repo.

All the performance cost is on our end, therefore our problem to deal
with; end-users should not really be affected. You can't fetch
unreachable commits (at least not by default, and we don't change that
default).