@@ -22,13 +22,15 @@ test_expect_success 'setup' '
22
22
: >foo &&
23
23
git add foo &&
24
24
git config i18n.commitEncoding iso8859-1 &&
25
- git commit -m "$added_iso88591" &&
25
+ echo "$added_iso88591" > commit-msg &&
26
+ git commit -F commit-msg &&
26
27
head1=$(git rev-parse --verify HEAD) &&
27
28
head1_short=$(git rev-parse --verify --short $head1) &&
28
29
tree1=$(git rev-parse --verify HEAD:) &&
29
30
tree1_short=$(git rev-parse --verify --short $tree1) &&
30
31
echo "$changed" > foo &&
31
- git commit -a -m "$changed_iso88591" &&
32
+ echo "$changed_iso88591" > commit-msg &&
33
+ git commit -a -F commit-msg &&
32
34
head2=$(git rev-parse --verify HEAD) &&
33
35
head2_short=$(git rev-parse --verify --short $head2) &&
34
36
tree2=$(git rev-parse --verify HEAD:) &&
@@ -206,13 +208,12 @@ test_expect_success '%C(auto) respects --color=auto (stdout not tty)' '
206
208
)
207
209
'
208
210
209
- iconv -f utf-8 -t iso8859-1 > commit-msg << EOF
210
- Test printing of complex bodies
211
+ printf " Test printing of complex bodies
211
212
212
213
This commit message is much longer than the others,
213
214
and it will be encoded in iso8859-1. We should therefore
214
- include an iso8859 character: ¡bueno !
215
- EOF
215
+ include an iso8859 character: \302\241bueno !
216
+ " | iconv -f utf-8 -t iso8859-1 > commit-msg
216
217
217
218
test_expect_success ' setup complex body' '
218
219
git config i18n.commitencoding iso8859-1 &&
0 commit comments