search

Flutter-Foundation / nest

Tools for hatching new Flutters
69 stars 2 forks source link

Consider patch-based approach to forking #10

Open selfisekai opened 1 day ago

selfisekai commented 1 day ago

I've listened to a bit of a talk on the space about handling Flock patches on top of alive Flutter branches/releases.

Electron is, I think, an interesting case for Flock to look at: it's a fast-moving, soft fork of Chromium, a gclient-based project.

It has a pretty specific approach: rather than constantly rebasing their repositories, they store git patches as files. The process of cloning Electron is quite literally cloning Chromium and a few extra repositories, then applying these patches on top of the upstream repositories locally.

https://github.com/electron/electron/blob/main/docs/development/patches.md

matthew-carroll commented 1 day ago

This seems like a very promising approach. Thanks for filing this.