4 ms·
> Then you’re maintaining a stack of patches on top of the upstream until the end of time The linked article has an ambitious solution for that, in the form of
by simonw 3mo ago
> Then you’re maintaining a stack of patches on top of the upstream until the end of time
The linked article has an ambitious solution for that, in the form of this prompt to a coding agent harness:
Set up a nightly cron job that
executes the prompt: fetch upstream
changes to the <software> and
rebase all local changes on
top of upstream. Check that the
software works as intended and
replace the current version.
- deleted 3mo ago[deleted]
- saltmate 3mo agoThat's not a solution, just the necessary work. You still have a stack of patches you continuously have to (have) rebase(d) on upstream.
- retropragma 3mo agoThat's why you only rebase when you actually need to in such cases. Another trick is to keep as few touch points into the original code as possible, preferring to keep most custom code in custom files.
- 1718627440 3mo agoThere are software tools like quilt, who do exactly that.