<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on Wilhelm Maritz</title><link>https://wjmaritz.dev/tags/git/</link><description>Recent content in Git on Wilhelm Maritz</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 31 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wjmaritz.dev/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>OneDrive and git fought over my vault. Both lost.</title><link>https://wjmaritz.dev/posts/onedrive-git-vault/</link><pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate><guid>https://wjmaritz.dev/posts/onedrive-git-vault/</guid><description>&lt;p>Over two days my Obsidian vault appeared to delete itself, git recorded 146 file deletions that never happened, and OneDrive spawned 120 conflict copies of notes I had just restored. Not one byte of a note was lost. Every failure traces back to a single sentence: two sync systems each believed they owned the same tree, and each interpreted the other&amp;rsquo;s behaviour as changes to sync.&lt;/p>
&lt;p>I have written this shape of post before. &lt;a href="https://wjmaritz.dev/posts/zimaboard-raid1-rebuild/">RAID1 saved my data but not the state around it&lt;/a>, and &lt;a href="https://wjmaritz.dev/posts/sqlite-trap-epilogue/">a trap I had published a warning about caught my own app the same day&lt;/a>. This one belongs to both families: the data was never in danger, the state lied about it, and the limit that made it all worse was documented in a workbook I had read and dismissed as something that happens to other people.&lt;/p></description></item></channel></rss>