<?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>File-Patch on Sentinel</title><link>https://sentinel-blog.cherrypod.org/tags/file-patch/</link><description>Recent content in File-Patch on Sentinel</description><image><title>Sentinel</title><url>https://sentinel-blog.cherrypod.org/images/social-preview.png</url><link>https://sentinel-blog.cherrypod.org/images/social-preview.png</link></image><generator>Hugo -- 0.147.0</generator><language>en-gb</language><lastBuildDate>Tue, 17 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sentinel-blog.cherrypod.org/tags/file-patch/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 48: Named Anchors</title><link>https://sentinel-blog.cherrypod.org/posts/48-anchor-allocator/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://sentinel-blog.cherrypod.org/posts/48-anchor-allocator/</guid><description>file_patch needs the planner to find a unique anchor string in existing code. The planner is bad at this. What if the system placed named markers instead?</description></item></channel></rss>