summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-06-25 09:24:50 (GMT)
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-25 23:52:16 (GMT)
commitaacc15ec5261fca8a02570f93028e3ac4213caae (patch)
tree876df2d64d285a7cd2d4624fa9657b4c0eab2602 /t
parent1abb3f14c872ac1b5b70db4334b21dde60e57b7a (diff)
downloadgit-aacc15ec5261fca8a02570f93028e3ac4213caae.zip
git-aacc15ec5261fca8a02570f93028e3ac4213caae.tar.gz
git-aacc15ec5261fca8a02570f93028e3ac4213caae.tar.bz2
[PATCH] git-merge-one-file-script: do not misinterpret rm failure.
When a merge adds a file DF and removes a directory there by deleting a path DF/DF, git-merge-one-file-script can be called for the removal of DF/DF when the path DF is already created by "git-read-tree -m -u". When this happens, we get confused by a failure return from 'rm -f -- "$4"' (where $4 is DF/DF); finding file DF there the "rm -f" command complains that DF is not a directory. What we want to ensure is that there is no file DF/DF in this case. Avoid getting ourselves confused by first checking if there is a file, and only then try to remove it (and check for failure from the "rm" command). Signed-off-by: Junio C Hamano <junkio@cox.net> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 't')
0 files changed, 0 insertions, 0 deletions