summaryrefslogtreecommitdiff
path: root/builtin/grep.c
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2021-09-10 10:29:55 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-09-10 22:46:34 (GMT)
commit3d40e3723b1bc86d22136ff01b0787809a3267a4 (patch)
tree23fd8b711d79e7598525e2f5ce8f9fc49b6c629e /builtin/grep.c
parent4dbf7f30b1d6469474d6a7e6759c9f84d305b95c (diff)
downloadgit-3d40e3723b1bc86d22136ff01b0787809a3267a4.zip
git-3d40e3723b1bc86d22136ff01b0787809a3267a4.tar.gz
git-3d40e3723b1bc86d22136ff01b0787809a3267a4.tar.bz2
stash: avoid feeding directories to update-index
When a file is removed from the cache, but there is a file of the same name present in the working directory, we would normally treat that file in the working directory as untracked. However, in the case of stash, doing that would prevent a simple 'git stash push', because the untracked file would be in the way of restoring the deleted file. git stash, however, blindly assumes that whatever is in the working directory for a deleted file is wanted and passes that path along to update-index. That causes problems when the working directory contains a directory with the same name as the deleted file. Add some code for this special case that will avoid passing directory names to update-index. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/grep.c')
0 files changed, 0 insertions, 0 deletions