<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operation Log on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/operation-log/</link><description>Recent content in Operation Log on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/operation-log/index.xml" rel="self" type="application/rss+xml"/><item><title>The Superpower of Undo: Navigating the Operation Log</title><link>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/operation-log-and-undo/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/jujutsu-vcs-guide-2026/operation-log-and-undo/</guid><description>&lt;p&gt;Have you ever made a change in your version control system, only to realize a few steps later that you&amp;rsquo;ve gone down the wrong path? Perhaps you accidentally squashed commits, rebased incorrectly, or simply wish you could rewind to a previous state without losing your work. In traditional VCS like Git, recovering from such scenarios can range from trivial to terrifying, often involving arcane commands or the dreaded &amp;ldquo;force push.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>