From af8a73d53983e5b7413860d7b78efea1d3342250 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 26 Aug 2019 16:41:24 -0400 Subject: [PATCH] noticed a problem --- .../direct_mode_upgrade_with_deleted_file.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/direct_mode_upgrade_with_deleted_file.mdwn diff --git a/doc/bugs/direct_mode_upgrade_with_deleted_file.mdwn b/doc/bugs/direct_mode_upgrade_with_deleted_file.mdwn new file mode 100644 index 0000000000..cec02a4a3a --- /dev/null +++ b/doc/bugs/direct_mode_upgrade_with_deleted_file.mdwn @@ -0,0 +1,16 @@ +Upgrading a direct mode repo to v7 while it has a deleted file in it +behaves strangely. This is after my recent change to not make it commit. + +A `git checkout` of the file checks out the pointer file, as the content +of the file is not present. This is as expected. + +But `git whereis` thinks the content is present, which it's not any longer. +Seems that the upgrade process needs to notice when a deleted file was the +only copy of the content, and set its content as not present. + +And `git fsck` doesn't find a problem, despite the content not being +present. And does not fix the location log. +This part may not be specific to this case, seems it must be some bug in +fsck? + +--[[Joey]]