summaryrefslogtreecommitdiff
path: root/t/t3903-stash.sh
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2019-10-30 10:49:37 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-11-02 06:22:00 (GMT)
commit8dfb04ae964868dda758997e5e7da29edff6164b (patch)
tree5d1eee5a858583ef426eb0086ec370d0899473e3 /t/t3903-stash.sh
parent5fa0f5238b0cd46cfe7f6fa76c3f526ea98148d9 (diff)
downloadgit-8dfb04ae964868dda758997e5e7da29edff6164b.zip
git-8dfb04ae964868dda758997e5e7da29edff6164b.tar.gz
git-8dfb04ae964868dda758997e5e7da29edff6164b.tar.bz2
update-index: optionally leave skip-worktree entries alone
While `git update-index` mostly ignores paths referring to index entries whose skip-worktree bit is set, in b4d1690df11 (Teach Git to respect skip-worktree bit (reading part), 2009-08-20), for reasons that are not entirely obvious, the `--remove` option was made special: it _does_ remove index entries even if their skip-worktree bit is set. Seeing as this behavior has been in place for a decade now, it does not make sense to change it. However, in preparation for fixing a bug in `git stash` where it pretends that skip-worktree entries have actually been removed, we need a mode where `git update-index` leaves all skip-worktree entries alone, even if the `--remove` option was passed. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3903-stash.sh')
0 files changed, 0 insertions, 0 deletions