git-filter-branch.sh: more portable tr usage: use \012, not \n.
I hesitate to suggest this, since GNU tr has accepted \n for 15 years, but there are supposedly a few crufty vendor-supplied versions of tr still in use. Also, all of the other uses of tr-with-newline in git use \012. Signed-off-by: Jim Meyering <meyering@redhat.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jim Meyering committed
Dec 18, 2007 at 11:03 UTC
e8a3f90994067a154fafcec9bbb18cf7865cd94c
1 file changed
+1
-1
git-filter-branch.sh
+1
-1
@@ -290,7 +290,7 @@ while read commit parents; do
290
eval "$filter_tree" < /dev/null ||
291
die "tree filter failed: $filter_tree"
292
293
- git diff-index -r $commit | cut -f 2- | tr '\n' '\000' | \
293
+ git diff-index -r $commit | cut -f 2- | tr '\012' '\000' | \
294
xargs -0 git update-index --add --replace --remove
295
git ls-files -z --others | \
296
xargs -0 git update-index --add --replace --remove