Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Added link to "Fossil Versus Git" article from our HACKERS.md, near where we are making similar (but less detailed) arguments. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
1be7a95d8e1d99d002dc995fa949c402 |
| User & Date: | tangent 2019-08-09 10:57:48 |
Context
|
2019-08-11
| ||
| 03:37 | Assorted improvements to the top-level README.md file. check-in: c3f1846968 user: tangent tags: trunk | |
|
2019-08-09
| ||
| 10:57 | Added link to "Fossil Versus Git" article from our HACKERS.md, near where we are making similar (but less detailed) arguments. check-in: 1be7a95d8e user: tangent tags: trunk | |
| 09:02 | Updated Autosetup. This is mainly an update to Jim Tcl 78 check-in: bc107cc50c user: tangent tags: trunk | |
Changes
Changes to HACKERS.md.
121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 |
While Fossil does allow offline operation and local independent clones, its default mode of operation is to try and keep the clones in sync as much as possible. Git works the way it does because it was designed to meet the needs of the Linux kernel development project, which is inherently federated, so Git tries to operate in a federated model as well. Fossil is better for smaller, more coherent teams, where there is a single, clear goal for the project and a single source for its official code. Fossil helps remote developers cooperate, whereas Git helps remote developers go off on their own tangents for extended periods of time and optionally sync back up with each other occasionally. Fossil is a better match for the way the PiDP-8/I software project works: we want you to cooperate closely with us, not go off on wild tangents. [gitwt]: https://git-scm.com/docs/git-worktree <a id="login"></a> Fossil Developer Access ---- If you have a developer account on the `tangentsoft.com/pidp8i` Fossil |
| | > > > > | |
121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 |
While Fossil does allow offline operation and local independent clones, its default mode of operation is to try and keep the clones in sync as much as possible. Git works the way it does because it was designed to meet the needs of the Linux kernel development project, which is inherently federated, so Git tries to operate in a federated model as well. Fossil is better for smaller, more coherent teams, where there is a single, clear goal for the project and a single primary host for its project repository. Fossil helps remote developers cooperate, whereas Git helps remote developers go off on their own tangents for extended periods of time and optionally sync back up with each other occasionally. Fossil is a better match for the way the PiDP-8/I software project works: we want you to cooperate closely with us, not go off on wild tangents. For more on this topic, see [Fossil Versus Git][fvg] in the Fossil documentation. [fvg]: https://fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki [gitwt]: https://git-scm.com/docs/git-worktree <a id="login"></a> Fossil Developer Access ---- If you have a developer account on the `tangentsoft.com/pidp8i` Fossil |