@ -129,14 +129,14 @@ Did you intend to checkout '$@' which can not be resolved as commit?"
@@ -129,14 +129,14 @@ Did you intend to checkout '$@' which can not be resolved as commit?"
# from a specific tree-ish; note that this is for
# rescuing paths and is never meant to remove what
if [ $(cat ../map/$src_head | wc -l) -gt 1 ]; then
echo "WARNING: Your commit filter caused the head commit to expand to several rewritten commits. Only the first such commit was recorded as the current $dstbranch head but you will need to resolve the situation now (probably by manually merging the other commits). These are all the commits:" >&2
sed 's/^/ /' ../map/$src_head >&2
@ -405,7 +405,7 @@ case "$target_head" in
@@ -405,7 +405,7 @@ case "$target_head" in
@ -113,10 +113,10 @@ for patch_name in $(cat "$QUILT_PATCHES/series" | grep -v '^#'); do
@@ -113,10 +113,10 @@ for patch_name in $(cat "$QUILT_PATCHES/series" | grep -v '^#'); do
git-ls-files --stage | sed -e 's/ '"$_x40"' / X /' >current &&
git ls-files --stage | sed -e 's/ '"$_x40"' / X /' >current &&
git diff expected current
}
# This is done on an empty work directory, which is the normal
# merge person behaviour.
test_expect_success \
'3-way merge with git-read-tree -m, empty cache' \
'3-way merge with git read-tree -m, empty cache' \
"rm -fr [NDMALTS][NDMALTSF] Z &&
rm .git/index &&
git-read-tree -m $tree_O $tree_A $tree_B &&
git read-tree -m $tree_O $tree_A $tree_B &&
check_result"
# This starts out with the first head, which is the normal
# patch submitter behaviour.
test_expect_success \
'3-way merge with git-read-tree -m, match H' \
'3-way merge with git read-tree -m, match H' \
"rm -fr [NDMALTS][NDMALTSF] Z &&
rm .git/index &&
git-read-tree $tree_A &&
git-checkout-index -f -u -a &&
git-read-tree -m $tree_O $tree_A $tree_B &&
git read-tree $tree_A &&
git checkout-index -f -u -a &&
git read-tree -m $tree_O $tree_A $tree_B &&
check_result"
: <<\END_OF_CASE_TABLE
@ -160,7 +160,7 @@ We have so far tested only empty index and clean-and-matching-A index
@@ -160,7 +160,7 @@ We have so far tested only empty index and clean-and-matching-A index
case which are trivial. Make sure index requirements are also
@ -11,7 +11,7 @@ There is the head (called H) and another commit (called M), which is
@@ -11,7 +11,7 @@ There is the head (called H) and another commit (called M), which is
simply ahead of H. The index and the work tree contains a state that
is derived from H, but may also have local changes. This test checks
all the combinations described in the two-tree merge "carry forward"
rules, found in <Documentation/git-read-tree.txt>.
rules, found in <Documentation/git read-tree.txt>.
In the test, these paths are used:
bozbar - in H, stays in M, modified from bozbar to gnusto
@ -23,7 +23,7 @@ In the test, these paths are used:
@@ -23,7 +23,7 @@ In the test, these paths are used:
@ -84,7 +84,7 @@ test_expect_success 'three-way not complaining on an untracked path in both' '
@@ -84,7 +84,7 @@ test_expect_success 'three-way not complaining on an untracked path in both' '
echo >file2 file two is untracked on the master side &&
echo >subdir/file2 file two is untracked on the master side &&
git-read-tree -m -u branch-point master side
git read-tree -m -u branch-point master side
'
test_expect_success 'three-way not clobbering a working tree file' '
@ -10,11 +10,11 @@ test_description='A simple turial in the form of a test case'
@@ -10,11 +10,11 @@ test_description='A simple turial in the form of a test case'
This test registers the following filesystem structure in the
cache:
@ -16,7 +16,7 @@ And then tries to checkout in a work tree that has the following:
@@ -16,7 +16,7 @@ And then tries to checkout in a work tree that has the following:
path0/file0 - a file in a directory
path1 - a file
The git-checkout-index command should fail when attempting to checkout
The git checkout-index command should fail when attempting to checkout
path0, finding it is occupied by a directory, and path1/file1, finding
path1 is occupied by a non-directory. With "-f" flag, it should remove
@ -13,22 +13,22 @@ handled. Specifically, that a bogus branch is not created.
@@ -13,22 +13,22 @@ handled. Specifically, that a bogus branch is not created.
test_expect_success \
'prepare a trivial repository' \
'echo Hello > A &&
git-update-index --add A &&
git update-index --add A &&
git-commit -m "Initial commit." &&
HEAD=$(git-rev-parse --verify HEAD)'
HEAD=$(git rev-parse --verify HEAD)'
test_expect_failure \
'git branch --help should not have created a bogus branch' \
test_description='Test of the various options to git-rm.'
test_description='Test of the various options to git rm.'
. ./test-lib.sh
@ -11,13 +11,13 @@ test_description='Test of the various options to git-rm.'
@@ -11,13 +11,13 @@ test_description='Test of the various options to git-rm.'