summaryrefslogtreecommitdiff
path: root/wiki/dev/merging-structural-changes.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/dev/merging-structural-changes.md')
-rw-r--r--wiki/dev/merging-structural-changes.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/wiki/dev/merging-structural-changes.md b/wiki/dev/merging-structural-changes.md
index 0c3970f..f597d39 100644
--- a/wiki/dev/merging-structural-changes.md
+++ b/wiki/dev/merging-structural-changes.md
@@ -76,3 +76,10 @@ diagram above shows how [Mercurial](http://www.selenic.com/mercurial/) handles
the same two tests. Since its changeset language does include an "object
moved" primitive, it's able to take a content change for `dir-a/file` and
apply it to `dir-b/file` if appropriate.
+
+## Git
+
+Git also gets this scenario right, _usually_. Unlike Mercurial, Git does not
+track file copies or renames in its commits at all, prefering to infer them by
+content comparison every time it performs a move-aware operation, such as a
+merge.