Git 2.53 Released With More Optimizations, One Step Closer To Making Rust Mandatory
https://www.phoronix.com/news/Git-2.53-Released
#Git 2.53 Released with New Features and Performance Improvements, Here's What's New https://9to5linux.com/git-2-53-released-with-new-features-and-performance-improvements
#Linux #OpenSource #FreeSoftware

Git 2.53 Released with New Features and Performance Improvements

rerere in git rerere stands for reduce reuse recycle
A new project status update has been posted on our opencollective page: https://opencollective.com/gothub/updates/web-interface-is-now-enabled-and-we-need-more-subscribers
#git #hosting #openbsd #gameoftrees
⚡️ PostgreSQL on Azure gets an AI upgrade
🏷️ #devdigest #azure #cloud #git #github
https://devdigest.today/goto/5307
I made deb packages for werge the weird-stuff-merging-mergetool, hopefully useful. https://github.com/exaexa/werge/releases/tag/v0.2.1.1
Side quest completed: #haskell #debian packaging workflow is <3
Сканер для обнаружения уязвимостей (NTLM relay)
#infosec #software #git #ad #pentest #relay
https://github.com/depthsecurity/RelayKing-Depth/
* Сканирует по SMB, LDAP/S, MSSQL, HTTP/S, RPC, WinRM;
* Находит WebDAV WebClient, CVE-2025-33073 (NTLM reflection), NTLMv1 + PrinterBug, PetitPotam и т.п.;
* Поддерживает аудит всего домена;
* Составляет список таргетов для `ntlmrelayx` и другого ПО;
* Сохраняет отчет в plaintext/JSON/CSV/Markdown.
Статья в блоге: https://www.depthsecurity.com/blog/introducing-relayking-relay-to-royalty/
All our #git repository hosting VMs have now been updated in production and are running the #gameoftrees web server gotwebd.
See here for how to configure the web server in gotsys.conf: https://gameoftrees.org/gotsys.conf.5.html#WEB_SERVER_CONFIGURATION
The web server name to use in the configuration is your subdomain.gothub.org
Custom domains can be added on request (and you'll need to set up an A record).
Ist es eine gute oder bescheuerte Idee das Home Verzeichnis komplett als git repo zu versionieren und in der .gitignore dann alles auszuschließen außer config/setting/dot files?
How awkward is it to merge a pull request into two different branches that will later be merged together?
(Yes, I’m still a novice when it comes to the collaborative part of collaborative git systems, no, I’m not planning on continuing this project with GitHub.)
I hate that the state of the internet has led me to this post. Ugh. I can’t even look up GitHub workflows without getting the “Workflow” branded automation.
Git Rev News Edition 131 (January 31st, 2026)
https://programming.dev/post/45073035