Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityTop Con
•••
Top Pro
•••Top Pro
•••
Top Pro
•••
Binary files (images, music... etc) are not handled so efficiently when there are many versions, since each version must be stored locally (which is unavoidable with distributed version management). nevertheless it is an issue. However, there is a git extension available (git LFS) that addresses this issue. See More
Mercurial makes it pretty darn hard to delete history by mistake. In Git, if you mistakenly commit to HEAD and switch to a different branch, your commit is toast. Yes, you can dig through the reflog but most users don't even know of its existence and will wish they didn't once they find out. See More
Fossil is secure: by design, it never forgets anything. This pilosophy makes it very difficult to mess up a repository, or lose data, by making a false maneuver. At the same time, Fossil does recognize that people do sometimes make mistakes. For example, it is possible to amend a commit message (much) later on. It is also possible to change a revision’s branch after the fact. See More
Git-annex doesn't necessarily store all content everywhere you use the repository. Instead, you can check out only the files you need right now. Git-annex figures out automatically from which remote to fetch files when you do need them. This doesn't require a server, the files can also be on some USB hard drives, in which case Git-annex will tell you which drive you need to connect to get a particular file. See More