|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='diff.*.textconv tests'
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
find_diff() {
|
|
|
|
sed '1,/^index /d' | sed '/^-- $/,$d'
|
|
|
|
}
|
|
|
|
|
|
|
|
cat >expect.binary <<'EOF'
|
|
|
|
Binary files a/file and b/file differ
|
|
|
|
EOF
|
|
|
|
|
|
|
|
cat >expect.text <<'EOF'
|
|
|
|
--- a/file
|
|
|
|
+++ b/file
|
|
|
|
@@ -1 +1,2 @@
|
|
|
|
0
|
|
|
|
+1
|
|
|
|
EOF
|
|
|
|
|
|
|
|
cat >hexdump <<'EOF'
|
|
|
|
#!/bin/sh
|
|
|
|
perl -e '$/ = undef; $_ = <>; s/./ord($&)/ge; print $_' < "$1"
|
|
|
|
EOF
|
|
|
|
chmod +x hexdump
|
|
|
|
|
|
|
|
test_expect_success 'setup binary file with history' '
|
|
|
|
printf "\\0\\n" >file &&
|
|
|
|
git add file &&
|
|
|
|
git commit -m one &&
|
|
|
|
printf "\\01\\n" >>file &&
|
|
|
|
git add file &&
|
|
|
|
git commit -m two
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'file is considered binary by porcelain' '
|
|
|
|
git diff HEAD^ HEAD >diff &&
|
|
|
|
find_diff <diff >actual &&
|
|
|
|
test_cmp expect.binary actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'file is considered binary by plumbing' '
|
|
|
|
git diff-tree -p HEAD^ HEAD >diff &&
|
|
|
|
find_diff <diff >actual &&
|
|
|
|
test_cmp expect.binary actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'setup textconv filters' '
|
|
|
|
echo file diff=foo >.gitattributes &&
|
|
|
|
git config diff.foo.textconv "\"$(pwd)\""/hexdump &&
|
|
|
|
git config diff.fail.textconv false
|
|
|
|
'
|
|
|
|
|
refactor userdiff textconv code
The original implementation of textconv put the conversion
into fill_mmfile. This was a bad idea for a number of
reasons:
- it made the semantics of fill_mmfile unclear. In some
cases, it was allocating data (if a text conversion
occurred), and in some cases not (if we could use the
data directly from the filespec). But the caller had
no idea which had happened, and so didn't know whether
the memory should be freed
- similarly, the caller had no idea if a text conversion
had occurred, and so didn't know whether the contents
should be treated as binary or not. This meant that we
incorrectly guessed that text-converted content was
binary and didn't actually show it (unless the user
overrode us with "diff.foo.binary = false", which then
created problems in plumbing where the text conversion
did _not_ occur)
- not all callers of fill_mmfile want the text contents. In
particular, we don't really want diffstat, whitespace
checks, patch id generation, etc, to look at the
converted contents.
This patch pulls the conversion code directly into
builtin_diff, so that we only see the conversion when
generating an actual patch. We also then know whether we are
doing a conversion, so we can check the binary-ness and free
the data from the mmfile appropriately (the previous version
leaked quite badly when text conversion was used)
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
16 years ago
|
|
|
test_expect_success 'diff produces text' '
|
|
|
|
git diff HEAD^ HEAD >diff &&
|
|
|
|
find_diff <diff >actual &&
|
|
|
|
test_cmp expect.text actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'diff-tree produces binary' '
|
|
|
|
git diff-tree -p HEAD^ HEAD >diff &&
|
|
|
|
find_diff <diff >actual &&
|
|
|
|
test_cmp expect.binary actual
|
|
|
|
'
|
|
|
|
|
refactor userdiff textconv code
The original implementation of textconv put the conversion
into fill_mmfile. This was a bad idea for a number of
reasons:
- it made the semantics of fill_mmfile unclear. In some
cases, it was allocating data (if a text conversion
occurred), and in some cases not (if we could use the
data directly from the filespec). But the caller had
no idea which had happened, and so didn't know whether
the memory should be freed
- similarly, the caller had no idea if a text conversion
had occurred, and so didn't know whether the contents
should be treated as binary or not. This meant that we
incorrectly guessed that text-converted content was
binary and didn't actually show it (unless the user
overrode us with "diff.foo.binary = false", which then
created problems in plumbing where the text conversion
did _not_ occur)
- not all callers of fill_mmfile want the text contents. In
particular, we don't really want diffstat, whitespace
checks, patch id generation, etc, to look at the
converted contents.
This patch pulls the conversion code directly into
builtin_diff, so that we only see the conversion when
generating an actual patch. We also then know whether we are
doing a conversion, so we can check the binary-ness and free
the data from the mmfile appropriately (the previous version
leaked quite badly when text conversion was used)
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
16 years ago
|
|
|
test_expect_success 'log produces text' '
|
|
|
|
git log -1 -p >log &&
|
|
|
|
find_diff <log >actual &&
|
|
|
|
test_cmp expect.text actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'format-patch produces binary' '
|
|
|
|
git format-patch --no-binary --stdout HEAD^ >patch &&
|
|
|
|
find_diff <patch >actual &&
|
|
|
|
test_cmp expect.binary actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'status -v produces text' '
|
|
|
|
git reset --soft HEAD^ &&
|
|
|
|
git status -v >diff &&
|
|
|
|
find_diff <diff >actual &&
|
|
|
|
test_cmp expect.text actual &&
|
|
|
|
git reset --soft HEAD@{1}
|
|
|
|
'
|
|
|
|
|
|
|
|
cat >expect.stat <<'EOF'
|
|
|
|
file | Bin 2 -> 4 bytes
|
|
|
|
1 files changed, 0 insertions(+), 0 deletions(-)
|
|
|
|
EOF
|
refactor userdiff textconv code
The original implementation of textconv put the conversion
into fill_mmfile. This was a bad idea for a number of
reasons:
- it made the semantics of fill_mmfile unclear. In some
cases, it was allocating data (if a text conversion
occurred), and in some cases not (if we could use the
data directly from the filespec). But the caller had
no idea which had happened, and so didn't know whether
the memory should be freed
- similarly, the caller had no idea if a text conversion
had occurred, and so didn't know whether the contents
should be treated as binary or not. This meant that we
incorrectly guessed that text-converted content was
binary and didn't actually show it (unless the user
overrode us with "diff.foo.binary = false", which then
created problems in plumbing where the text conversion
did _not_ occur)
- not all callers of fill_mmfile want the text contents. In
particular, we don't really want diffstat, whitespace
checks, patch id generation, etc, to look at the
converted contents.
This patch pulls the conversion code directly into
builtin_diff, so that we only see the conversion when
generating an actual patch. We also then know whether we are
doing a conversion, so we can check the binary-ness and free
the data from the mmfile appropriately (the previous version
leaked quite badly when text conversion was used)
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
16 years ago
|
|
|
test_expect_success 'diffstat does not run textconv' '
|
|
|
|
echo file diff=fail >.gitattributes &&
|
|
|
|
git diff --stat HEAD^ HEAD >actual &&
|
|
|
|
test_cmp expect.stat actual
|
|
|
|
'
|
|
|
|
# restore working setup
|
|
|
|
echo file diff=foo >.gitattributes
|
|
|
|
|
|
|
|
cat >expect.typechange <<'EOF'
|
|
|
|
--- a/file
|
|
|
|
+++ /dev/null
|
|
|
|
@@ -1,2 +0,0 @@
|
|
|
|
-0
|
|
|
|
-1
|
|
|
|
diff --git a/file b/file
|
|
|
|
new file mode 120000
|
|
|
|
index 0000000..67be421
|
|
|
|
--- /dev/null
|
|
|
|
+++ b/file
|
|
|
|
@@ -0,0 +1 @@
|
|
|
|
+frotz
|
|
|
|
\ No newline at end of file
|
|
|
|
EOF
|
|
|
|
# make a symlink the hard way that works on symlink-challenged file systems
|
|
|
|
test_expect_success 'textconv does not act on symlinks' '
|
|
|
|
printf frotz > file &&
|
|
|
|
git add file &&
|
|
|
|
git ls-files -s | sed -e s/100644/120000/ |
|
|
|
|
git update-index --index-info &&
|
|
|
|
git commit -m typechange &&
|
|
|
|
git show >diff &&
|
|
|
|
find_diff <diff >actual &&
|
|
|
|
test_cmp expect.typechange actual
|
|
|
|
'
|
|
|
|
|
|
|
|
test_done
|