Modifying Other People's Software | natkr's ramblings
https://natkr.com/2025-08-14-modifying-other-peoples-software/
What if we could just.. import our patchset into Git, at the start of our session, and then export it back out as a series of patch files when we're done? That way we're effectively following the commandments of The Holy Quiltmother, but still get to keep our familiar Git UI.
pre dev wiki: Applying Patches
http://predev.wikidot.com/applying-patches
quilt - Summary [Savannah]
http://savannah.nongnu.org/projects/quilt
"The scripts allow to manage a series of patches by keeping track of the changes each patch makes. Patches can be applied, un-applied, refreshed, etc." Checkpoint and maintain floating uncommitted work-in-progress changes as a stack of patches atop a moving-target project.
Links » Quilt and SVN: A Slightly Unhappy Marriage
http://www.links.org/?p=278
"The issue comes when you finally get approval for your patch and you commit it to the tree. At this point, you want to delete it from the patch series - but quilt won’t let you, because it is applied. If you pop it, then you’ll undo what you’ve just committed. So, what to do? Here’s my ad-hoc recipe"
Making quilt and subversion work together | Carfax
http://www.carfax.org.uk/node/35
"apply the current quilt patch to the subversion repository, commit it using the patch comments from quilt as the commit message, and remove the patch from the quilt patch series."