undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Side-step sed line-ending "corruption" leading to t6038 failure.

Browse Source 
By default, MSYS sed throws away CR from CRLF line-endings.  Tests
t6038.5 and t6038.6 employ sed to normalize conflict output of git-merge
for validation purposes.  These tests expect CRLF line-endings to be
present in the normalized output of git-merge, and thus fail when sed
undesirably removes CR.  Fix by employing sed's -b/--binary switch to
suppress its default behavior of dropping CR characters.

Acked-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
This commit is contained in:
Eric Sunshine 2010-09-17 09:16:01 -04:00 committed by Pat Thoyts
parent 97f2c33a52
commit ca02ad3447
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
t/t6038-merge-text-auto.sh
View File

@ -14,6 +14,8 @@ test_description='CRLF merge conflict across text=auto change
. ./test-lib.sh . ./test-lib.sh
test_have_prereq MINGW && SED_OPTIONS=-b
test_expect_success setup ' test_expect_success setup '
git config core.autocrlf false && git config core.autocrlf false &&
@ -60,7 +62,7 @@ test_expect_success setup '
test_expect_success 'set up fuzz_conflict() helper' ' test_expect_success 'set up fuzz_conflict() helper' '
fuzz_conflict() { fuzz_conflict() {
sed -e "s/^\([<>=]......\) .*/\1/" "$@" sed $SED_OPTIONS -e "s/^\([<>=]......\) .*/\1/" "$@"
} }
' '