Brad King wrote:
> Add test cases that use 'merge-recursive' plumbing with a temporary
> index and empty work tree. Populate the index using 'read-tree' and
> 'update-index --ignore-missing --refresh' to prepare for merge without
> actually checking all files out to disk. Verify that each merge
> produces its expected tree while displaying no error diagnostics.
Following my usual review practice of lazy reading for the sake of
readers in the future who might be in a hurry, it's not clear what
problem these tests are solving or trying to detect. Could you start
with a quick summary of the symptoms and when it came up?
The commit message doesn't need to paraphrase the actual code, since
anyone curious about the details can always look at the code. It's
more important to explain the motivation and intended effect so people
can understand what went wrong if something ends up being broken by a
> This approach can be used to compute tree merges while checking out only
> conflicting files to disk (which is useful for server-side scripts).
> Prior to commit 5b448b85 (merge-recursive: When we detect we can skip an
> update, actually skip it, 2011-08-11) this worked cleanly in all cases.
Do you mean something like the following?
Sometimes when working with a large repository it can be useful to
try out a merge and only check out conflicting files to disk (for
example as a speed optimization on a server). Until v1.7.7-rc1~28^2~20
(merge-recursive: When we detect we can skip an update, actually
skip it, 2011-08-11), it was possible to do so with the following
... summary of commands here ...
Nowadays, that still works and the exit status is the same,
but merge-recursive produces a diagnostic if "our" side renamed
error: addinfo_cache failed for path 'dst'
Add a test to document this regression.
> +++ b/t/t3030-merge-recursive.sh
> @@ -517,6 +518,52 @@ test_expect_success 'reset and bind merge' '
> +test_expect_failure 'merge-recursive w/ empty work tree - ours has rename' '
> + (
> + GIT_WORK_TREE="$PWD/ours-has-rename-work" &&
Elsewhere in the test, commands in a subshell are indented by another
tab, so these new tests should probably follow suit. As a side
effect, that makes the indentation easier to see.
Hope that helps,
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html