author | Jeff King <peff@peff.net> | |
Fri, 29 Apr 2011 22:23:54 +0000 (18:23 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Fri, 29 Apr 2011 22:37:08 +0000 (15:37 -0700) | ||
commit | cf1af1b1f3ddd2554f64aae120635952801a9632 | |
tree | 87d8f1696565764f3822afdc6889fcee22d0d2b7 | tree | snapshot |
parent | 547e8b9205349b47003ed25a82673e413e71c255 | commit | diff |
add tests for merge-index / merge-one-file
There were no tests for either, except a brief use in
t1200-tutorial.
These tools are not used much these days, as most people
use the merge-recursive strategy, which handles everything
internally. However, they are used by the "octopus" and
"resolve" strategies, as well as any custom strategies
or merge scripts people have built around them.
For example, together with read-tree, they are the simplest
way to do a basic content-level merge without checking out
the entire repository contents beforehand.
This script adds a basic test of the tools to perform one
content-level merge. It also shows a failure of the tools to
work properly in the face of GIT_WORK_TREE or core.worktree.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
There were no tests for either, except a brief use in
t1200-tutorial.
These tools are not used much these days, as most people
use the merge-recursive strategy, which handles everything
internally. However, they are used by the "octopus" and
"resolve" strategies, as well as any custom strategies
or merge scripts people have built around them.
For example, together with read-tree, they are the simplest
way to do a basic content-level merge without checking out
the entire repository contents beforehand.
This script adds a basic test of the tools to perform one
content-level merge. It also shows a failure of the tools to
work properly in the face of GIT_WORK_TREE or core.worktree.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t6060-merge-index.sh | [new file with mode: 0755] | blob |