From f226b34b3701a7887a63046400f122cbb7296424 Mon Sep 17 00:00:00 2001 From: anarcat Date: Tue, 11 Dec 2018 17:06:19 +0000 Subject: [PATCH] Added a comment: possibly --- ...ent_6_65a5c2ca20f1efbf94e2b1d5309ddecc._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/why_are_all_those_files_modified/comment_6_65a5c2ca20f1efbf94e2b1d5309ddecc._comment diff --git a/doc/forum/why_are_all_those_files_modified/comment_6_65a5c2ca20f1efbf94e2b1d5309ddecc._comment b/doc/forum/why_are_all_those_files_modified/comment_6_65a5c2ca20f1efbf94e2b1d5309ddecc._comment new file mode 100644 index 0000000000..165556cabb --- /dev/null +++ b/doc/forum/why_are_all_those_files_modified/comment_6_65a5c2ca20f1efbf94e2b1d5309ddecc._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="anarcat" + avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7" + subject="possibly" + date="2018-12-11T17:06:19Z" + content=""" +> Does that sequence match what you were doing? I didn't reproduce the problem when just upgrading the v5 and then getting the unlocked files into it. + +I don't *exactly* remember, unfortunately, but that seems likely. It matches my previous comment, which indicates I upgraded to the backport *after* filing the bug report anyways. + +> Seems that the upgrade to v7 process, after scanning for and populating unlocked files, needs to update git's index. I thought it did, but perhaps I forgot or that is not working. + +Makes sense! :) +"""]]