<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tooling on Luis Tineo</title><link>https://www.kingletas.com/tags/tooling/</link><description>Recent content in Tooling on Luis Tineo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.kingletas.com/tags/tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>The dry run that checked nothing</title><link>https://www.kingletas.com/posts/2026/the-dry-run-that-checked-nothing/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.kingletas.com/posts/2026/the-dry-run-that-checked-nothing/</guid><description>A script for keeping GitHub repositories on the same settings said everything was fine when it had checked nothing. It did it three different ways in four days, and one of those causes is still a best guess.</description></item><item><title>Two loops waiting for themselves</title><link>https://www.kingletas.com/posts/2026/two-loops-waiting-for-themselves/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.kingletas.com/posts/2026/two-loops-waiting-for-themselves/</guid><description>Two background waits ran for 94 minutes on an install that had finished at roughly minute four. Each one was waiting for its own exit, the command used to look for them hid them, and the first fix hung the same way.</description></item></channel></rss>