<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: svyatoslavpavl</title><link>https://news.ycombinator.com/user?id=svyatoslavpavl</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 20 Aug 2026 16:25:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=svyatoslavpavl" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by svyatoslavpavl in "Splitting a Git Commit"]]></title><description><![CDATA[
<p>hadn't thought of building forward like that. being able to test each slice before committing beats finding out after the rebase that half of them don't compile. thanks, stealing this</p>
]]></description><pubDate>Wed, 19 Aug 2026 20:17:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=49366633</link><dc:creator>svyatoslavpavl</dc:creator><comments>https://news.ycombinator.com/item?id=49366633</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49366633</guid></item><item><title><![CDATA[New comment by svyatoslavpavl in "Splitting a Git Commit"]]></title><description><![CDATA[
<p>The bit that made this click for me: it works on any commit in history, not just HEAD. Mark the commit as edit in git rebase -i, then git reset HEAD^ to uncommit it while keeping the changes in the working tree, and rebuild the pieces from there.<p>git add -p is the real workhorse for the rebuild: s splits a hunk into smaller ones, and e lets you hand-edit the hunk when the boundary doesn't fall on clean line breaks. Stage a coherent slice, git commit, repeat until the tree is empty, then git rebase --continue. The rebase's only job is to drop you at the right spot; add -p does the actual splitting.</p>
]]></description><pubDate>Tue, 18 Aug 2026 15:46:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=49347473</link><dc:creator>svyatoslavpavl</dc:creator><comments>https://news.ycombinator.com/item?id=49347473</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49347473</guid></item></channel></rss>