Wusstet ihr, dass `git blame` eigentlich `git praise` heißen sollte? 🤔

Stattdessen starrt man auf Zeilen von 2019 und fragt sich, wer um 23:47 Uhr nüchtern "temporäre Lösung" in den main gepusht hat.

(Spoiler: Man selbst.)

Versionskontrolle ist Archäologie – nur dass die Artefakte manchmal noch in Produktion laufen. 🏺💻

#git #OpenSource #DevLife #Programmieren

Zum Wochenende: Lex Git - Gesetze diffen

Der Autor fragt sich, ob man Git für synoptische Vergleiche von Gesetzen verwenden kann. Lassen sich Gesetze mit Software vergleichen?

#Gesetze #Vergleich #Synopse #Git #Linux

https://gnulinux.ch/zum-wochenende-lex-git-gesetze-diffen

I wrote up how I've been attributing usage of AI models & coding agent harnesses when drafting code commits: https://dafoster.net/articles/2026/04/17/ai-attribution-in-git/ #aicoding #git

Well that's me all confuzzled with Git. Again.

Commit changes
Make more changes
Open Kraken
YOU ARE DETACHED HEAD!! Proceed no further! make NEW Branch to preserve Changes! Bad Coder! No Cookie!
Commit changes
All looks well.

Am I good? What's going on?

#git #gamedev #kraken #gitkraken #godot #gdscript #godotengine

I submitted a Pull Request to update MacPorts' Got (Game of Trees) to 0.124 here:

https://github.com/macports/macports-ports/pull/32238

GitHub Continuous Integration checks passed OK!

It's up to someone else with commit access to merge it.

I'm excited about the UTF-8 improvements in this release!

#Got #GameOfTrees #MacPorts #VersionControl #Git #OpenSource

Game of Trees 0.124 released https://www.undeadly.org/cgi?action=article;sid=20260413125436 #openbsd #got #git #gameoftrees #development #gothub #versioncontrol #libresoftware #freesoftware

so, trying to understand #git...

let's say i have an internal ForgeJo instance at git.example.org. i pull src.git from git.freebsd.org and push it to git.example.org, and now i can pull it on all my dev VMs.

now i want to commit a change, but i don't want to give my dev VM access to my FreeBSD SSH key. so, i make the change on dev, test and commit it, then push it to git.example.org.

then, on my desktop, i pull from git.example.org and push to gitrepo.freebsd.org. but, in the mean time, someone has has pushed another commit to gitrepo.freebsd.org, so i have to rebase and push again.

now i can't push my rebased local branch back to git.freebsd.org without doing a force push, which will break all my clones.

what's the right way to do this?

Game of Trees 0.123 released https://www.undeadly.org/cgi?action=article;sid=20260226054524 #openbsd #gameoftrees #got #git #gothub #development #programming #versioncontrol #sourcecontrol

Game of Trees 0.122 released https://www.undeadly.org/cgi?action=article;sid=20260211061627 #openbsd #got #git #gameoftrees #versioncontrol #development #freesoftware #libresoftware

Same thing happened to me with #git and Linux earlier. Now that I think about it, I'm surprised I learned gdb CLI so late.

Game of Trees 0.121 released https://www.undeadly.org/cgi?action=article;sid=20260201110851 #openbsd #gameoftrees #got #git #development #sourcecontrol #versioncontrol #freesoftware #libresoftware

I was working on updating a #cpp project to a newer #Qt version, but wanted to keep comparing to a #git tag from some time ago. The problem is that checking out a different commit changes all the files as far as #CMake is concerned, and everything builds from scratch. If only there was a way to have another copy of the same repo without cloning...

pipx install nb-clean
nb-clean add-filter --remove-empty-cells --preserve-cell-outputs