54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
uncommon for no repository in the project to hold all the different code
versions for a project. Instead the information is distributed.
Individual developers have one or more private branches. A hierarchy
of integrators merge changes from individual developers into collaborative
branches, until all the changes are merged together at the top-level master
branch. And all of this can be accomplished without having to have all the
code in any one repository. Developers or groups of developers can share
only those branches that they want to share and keep other branchs of the
project private. This is analogous to sharding an a distributed database.
Fossil allows private branches, but its default mode is to share everything.
And so in a Fossil project, all repositories tend to contain all of the
content at all times. This is analogous to replication in a
distributed database.
|
|
|
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
uncommon for no repository in the project to hold all the different code
versions for a project. Instead the information is distributed.
Individual developers have one or more private branches. A hierarchy
of integrators merge changes from individual developers into collaborative
branches, until all the changes are merged together at the top-level master
branch. And all of this can be accomplished without having to have all the
code in any one repository. Developers or groups of developers can share
only those branches that they want to share and keep other branches of the
project private. This is analogous to sharding an a distributed database.
Fossil allows private branches, but its default mode is to share everything.
And so in a Fossil project, all repositories tend to contain all of the
content at all times. This is analogous to replication in a
distributed database.
|
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
|
Git features the "rebase" command which can be used to change the
sequence of check-ins in the repository. Rebase can be used to "clean up"
a complex sequence of check-ins to make their intent easier for others
to understand. This is important if you view the history of a project
as part of the documentation for the project.
Fossil takes an opposing view. Fossil views history as sacrosanct and
stubornly refuses to change it.
Fossil allows mistakes to be corrected (for example, check-in comments
can be revised, and check-ins can be moved onto new branches even after
the check-in has occurred) but the correction is an addition to the repository
and the original actions are preserved and displayed alongside
the corrections, thus preserving an historically accurate audit trail.
This is analogous to an accounting practice of marking through an incorrect
entry in a ledger and writing a correction beside it.
|
|
|
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
|
Git features the "rebase" command which can be used to change the
sequence of check-ins in the repository. Rebase can be used to "clean up"
a complex sequence of check-ins to make their intent easier for others
to understand. This is important if you view the history of a project
as part of the documentation for the project.
Fossil takes an opposing view. Fossil views history as sacrosanct and
stubbornly refuses to change it.
Fossil allows mistakes to be corrected (for example, check-in comments
can be revised, and check-ins can be moved onto new branches even after
the check-in has occurred) but the correction is an addition to the repository
and the original actions are preserved and displayed alongside
the corrections, thus preserving an historically accurate audit trail.
This is analogous to an accounting practice of marking through an incorrect
entry in a ledger and writing a correction beside it.
|