* [PATCH] git-filter-branch.sh: more portable tr usage: use \012, not \n.
@ 2007-12-18 10:03 Jim Meyering
0 siblings, 0 replies; only message in thread
From: Jim Meyering @ 2007-12-18 10:03 UTC (permalink / raw)
To: git list
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>
---
git-filter-branch.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-filter-branch.sh b/git-filter-branch.sh
index 3bb2f67..ee9e1b3 100755
--- a/git-filter-branch.sh
+++ b/git-filter-branch.sh
@@ -290,7 +290,7 @@ while read commit parents; do
eval "$filter_tree" < /dev/null ||
die "tree filter failed: $filter_tree"
- git diff-index -r $commit | cut -f 2- | tr '\n' '\000' | \
+ git diff-index -r $commit | cut -f 2- | tr '\012' '\000' | \
xargs -0 git update-index --add --replace --remove
git ls-files -z --others | \
xargs -0 git update-index --add --replace --remove
--
1.5.4.rc0.53.gdfcd
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2007-12-18 10:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-18 10:03 [PATCH] git-filter-branch.sh: more portable tr usage: use \012, not \n Jim Meyering
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox