From 471bcfaf37421742e0901b07ed51772a0413530a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Oct 2020 14:51:19 -0400 Subject: [PATCH] comment --- ...0_094362fc0257e3c15bf2059520fc22cf._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/clarify_that_v7_applies_to_all_clones/comment_10_094362fc0257e3c15bf2059520fc22cf._comment diff --git a/doc/todo/clarify_that_v7_applies_to_all_clones/comment_10_094362fc0257e3c15bf2059520fc22cf._comment b/doc/todo/clarify_that_v7_applies_to_all_clones/comment_10_094362fc0257e3c15bf2059520fc22cf._comment new file mode 100644 index 0000000000..5a589959d6 --- /dev/null +++ b/doc/todo/clarify_that_v7_applies_to_all_clones/comment_10_094362fc0257e3c15bf2059520fc22cf._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 10""" + date="2020-10-05T18:40:32Z" + content=""" +Unless it entered an adjusted unlocked branch, this upgrade cannot have +changed locked files to unlocked files itself. So if you were not using +unlocked files in this repo before, and didn't make any changes after the +upgrade that would add any, you don't need to worry about them. + +The only risk if it was downgraded to v5 with an unlocked files +is that a command like `git commit -a` would commit the +large content to git. Easy enough to notice that with `git status` after +the downgrade too. + +(But do checkout master if the currently checked out branch is +"adjusted/master(unlocked)") +"""]]