7f311eb54b
The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.
The backquoted form is the traditional method for command
substitution, and is supported by POSIX. However, all but the
simplest uses become complicated quickly. In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.
The patch was generated by:
for _f in $(find . -name "*.sh")
do
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
and then carefully proof-read.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
28 lines
413 B
Bash
Executable File
28 lines
413 B
Bash
Executable File
#!/bin/sh
|
|
#
|
|
# Copyright (c) 2006 Junio C Hamano
|
|
#
|
|
|
|
test_description='git read-tree --prefix test.
|
|
'
|
|
|
|
. ./test-lib.sh
|
|
|
|
test_expect_success setup '
|
|
echo hello >one &&
|
|
git update-index --add one &&
|
|
tree=$(git write-tree) &&
|
|
echo tree is $tree
|
|
'
|
|
|
|
echo 'one
|
|
two/one' >expect
|
|
|
|
test_expect_success 'read-tree --prefix' '
|
|
git read-tree --prefix=two/ $tree &&
|
|
git ls-files >actual &&
|
|
cmp expect actual
|
|
'
|
|
|
|
test_done
|