5 ms·
What this makes me wonder is whether there could be a way for GitHub or its equivalents to make the concept of “a fork by patching” a first-class concept. I’ve
by zellyn 3y ago
What this makes me wonder is whether there could be a way for GitHub or its equivalents to make the concept of “a fork by patching” a first-class concept.
I’ve definitely done this for company-internal forks by trying to keep the changes as a clean list of linear commits that can be rebased as easily as possible, but it’s interesting to imagine what purpose-built tooling could do to facilitate maintaining such a patch-based fork.
- Karellen 3y agoThere's always `quilt` https://savannah.nongnu.org/projects/quilt https://savannah.nongnu.org/projects/quilt https://manpages.debian.org/bookworm/quilt/quilt.1.en.html https://manpages.debian.org/bookworm/quilt/quilt.1.en.html
- foxhop 3y agoa set of patches to run on the Repo works but it breaks when a big refactor happens upstream.
- PartiallyTyped 3y agoI think at some point you will diverge to the point that sync-ing or submitting patches is unmanageable. I heard stories of projects where every X weeks a person gets assigned to syncing, and it's almost guaranteed that the person will quit soon after. The team even had a tool to assist with the process.