dn42/wiki
1
Fork 0
mirror of https://git.dn42.dev/wiki/wiki.git synced 2025-03-13 09:04:27 +01:00
Code Releases Activity

Updated FAQ (markdown)

Browse Source
This commit is contained in:
dn42 wiki 2017-06-08 14:29:55 +00:00
parent 3f26ebac1b
commit 99e7c5d2b1
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
FAQ.md
View File

@ -4,7 +4,7 @@
### Why are you using monotone for the registry? Why not Git?
There is an important difference between the data model of monotone and Git: In Git branches *are* HEADs, while in monotone, branches are a list of HEADs. Or, to state it simpler and probably less correct: It is possible to sync merge conflicts in monotone. In Git, conflicts are part of the index and/or working tree, and thus can't be pushed/pulled.
There is an important difference between the data model of monotone and Git: In Git branches *are* heads, while in monotone, branches are a list of heads. Or, to state it simpler and probably less correct: It is possible to sync merge conflicts in monotone. In Git, conflicts are part of the index and/or working tree, and thus can't be pushed/pulled.
The DN42 registry is stored on multiple monotone servers which sync with each other. This is not possible in Git, because the Git servers don't know how to handle merge conflicts. In monotone, the servers just sync the conflict.