aboutsummaryrefslogtreecommitdiffstats
path: root/using-git.texinfo
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-09-16 18:13:59 +0200
committerMattias Andrée <maandree@operamail.com>2013-09-16 18:13:59 +0200
commitf82d7a97f143f5e68c241eeda4bbf9f1350f78b6 (patch)
tree3db935089b2d8ef5b648b2eec7b72ead1752e9c2 /using-git.texinfo
parenton perservation of timestamps (diff)
downloadusing-git-f82d7a97f143f5e68c241eeda4bbf9f1350f78b6.tar.gz
using-git-f82d7a97f143f5e68c241eeda4bbf9f1350f78b6.tar.bz2
using-git-f82d7a97f143f5e68c241eeda4bbf9f1350f78b6.tar.xz
on custom automatic merge tools
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to 'using-git.texinfo')
-rw-r--r--using-git.texinfo21
1 files changed, 19 insertions, 2 deletions
diff --git a/using-git.texinfo b/using-git.texinfo
index 3722ec0..e6c6023 100644
--- a/using-git.texinfo
+++ b/using-git.texinfo
@@ -1304,6 +1304,7 @@ is annoying.
@menu
* Git and permissions::
* Git and timestamps::
+* Git and custom merge tools::
@end menu
@@ -1385,6 +1386,22 @@ other reason it needs to.
+@node Git and custom merge tools
+@section Git and custom merge tools
+
+Git lets you use custom automatic merge tools.
+This can be used, for example, to merge binary
+file formats. It is possible to use a merge
+tool to required human interaction, however,
+this is discouraged because than the commit
+history will have no indication that there
+was a merge conflict. You can use a merge tool
+that tries to merge and marks all conflicts,
+and then manually use a tool the lets you
+see the conflicts and resolve.
+
+
+
@node Beyond Git
@chapter Beyond Git
@@ -1404,8 +1421,8 @@ other reason it needs to.
Git is used for source control, for
a complete, possibily collaborative,
-development environment you additional
-tools.
+development environment you need
+additional tools.
Everything git can do, you can do in
the command line, but some repetitive