1. 17

  2. 5

    So this means that they completely discarded the history of their own repository up to yesterday. Just check it out, there’s only one patch: https://nest.pijul.com/pijul_org/pijul/patches. Doing this sort of thing with a version control system seems like a strange decision to me.

    1. 1

      Makes it look like perhaps they went self-hosting too early.

    2. 5

      Pijul’s focus on patches (as opposed to snapshots) could allow it to handle giant repositories with a very large number of files, like in the case of “monorepos”. In particular, even though the commands are not yet implemented, the theory and algorithms allow for partial checkouts. “Partial” here means cloning just a subfolder of a repository, and still producing patches that can interact with the rest of the repository.

      This is not just about monorepos. Fine granular access permissions is the one advantage Subversion still has over distributed VCSs.