4 ms·
I have always been an advocate of forking, despite the overhead of maintaining patches, but porting patches should be trivial to automate now. There needs to be
by deckar01 8mo ago
I have always been an advocate of forking, despite the overhead of maintaining patches, but porting patches should be trivial to automate now. There needs to be an easy way to publish, discover, and require community patches even if they don’t have the maintainer’s blessing.
- eviks 8mo agoHow can you trivially automate conflicting changes?
- 112233 8mo agoIsn't porting patches the equivalent of a halting problem? Or did you have something specific in mind?
- frou_dh 8mo agoThe whole GitHub paradigm has muddied the meaning of the term "forking". It used to imply a serious intention to diverge. Now to a lot of people it just means doing any development on a copy of a repo. The "Fork" button on GitHub is really "Clone (to my account)".