3 ms·

I'm confused, is this just patch and apply patch?

• alexjurkiewicz 1y ago
  Yes. It's a small DSL to fork a repository and apply a series of textfile transformations (replace file, replace partial file). But if you give this a cool name, it's a New Idea.
  • worldsayshi 1y ago
    So it's a fork but with somewhat semantic diff specifications?
    • SOLAR_FIELDS 1y ago
      Yes, specifications which could almost certainly be applied with a custom merge drivers or strategy rather than trying to come up with a clever name and hand baking a custom toolchain to do what you can already do with Git
      • SoftTalker 1y ago
        Not all projects use git.
        • 90s_dev 1y ago
          Weird.
        • SOLAR_FIELDS 1y ago
          How many of those projects are attempts at maintaining patches across multiple upstreams, where none of those upstream projects use Git? The author freely admits in their post that all upstream projects in their case are using git, like most of the FOSS world. They just chose fossil for their downstream project because Reasons.
  • knowitnone 1y ago
    did you say "fork"?
  • dunham 1y ago
    The TeX source works like this, too. There is the original tex.web and some change files which get applied when converting it to either a TeX document or pascal source. (These days the pascal is further translated to C.)