summaryrefslogtreecommitdiff
path: root/git-pull.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2007-05-25 23:42:36 -0400
committerLibravatar Junio C Hamano <junkio@cox.net>2007-05-25 21:43:33 -0700
commit4b7cc26a74b01ceab14a32ef66704557b26d5622 (patch)
tree2719dd1ecc701a0979f440d6b1e9f26e6c590fb4 /git-pull.sh
parentDocumentation: Add definition of "evil merge" to GIT Glossary (diff)
downloadtgif-4b7cc26a74b01ceab14a32ef66704557b26d5622.tar.xz
git-am: use printf instead of echo on user-supplied strings
Under some implementations of echo (such as that provided by dash), backslash escapes are recognized without any other options. This means that echo-ing user-supplied strings may cause any backslash sequences in them to be converted. Using printf resolves the ambiguity. This bug can be seen when using git-am to apply a patch whose subject contains the character sequence "\n"; the characters are converted to a literal newline. Noticed by Szekeres Istvan. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'git-pull.sh')
0 files changed, 0 insertions, 0 deletions