Aktuelle Änderungen
Printable View
Änderungen
Bearbeiten
Homoiconicity > LazyEvaluation > EmacsSolutions > RichardGabriel > CodeCompletion > AutoCompletion > TotalCommander > UsefulTools > XmlWithClojure > GuidoVanRossum > ImplicitTyping > HygienicMacros > SyntacticSugar > TabbedBrowsing > ProperTailCall > Recursion > MercurialVsGitClear Trail
DistributedVersionControlSystems
Mercurial
Git
Pros, Cons, and some Facts.
- Mercurial has problems with large binary files
- http://martinfowler.com/bliki/VersionControlTools.html
- Mercurial generally makes no assumptions about file contents. Thus, most things in Mercurial work fine with any type of file.
- Secondly, our storage format currently uses signed 32-bit values for recording file sizes. That gives us a hard limit of 2GiB.
- Git is not well supported for Windows. Mercurial is natively supported.
- Mercurial is elegant. -> James Bond [1]
- Mercurials internalt structures are less mutable (more secure?) [2]
- Mercurials internal structures are more complex.
- just a fact: Git infers renames (different filename, same content) [3]
- Git uses snapshots, Mercurial's history is based on changesets
- Mercurials administrative files take less space (changeset-oriented vs. Git's snapshot-orientation).
- Mercurial's branches are infered - not explicit.