From 3ba349eec354d5b5ac14fae3a86614883a234eb8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 22 Feb 2021 12:38:34 -0400 Subject: [PATCH] comment --- ..._7ea295a6c113ea0cc3e4e5ae28769190._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/bugs/no_way_to_disable_repository_auto_upgrade/comment_4_7ea295a6c113ea0cc3e4e5ae28769190._comment diff --git a/doc/bugs/no_way_to_disable_repository_auto_upgrade/comment_4_7ea295a6c113ea0cc3e4e5ae28769190._comment b/doc/bugs/no_way_to_disable_repository_auto_upgrade/comment_4_7ea295a6c113ea0cc3e4e5ae28769190._comment new file mode 100644 index 0000000000..7945b1f8b4 --- /dev/null +++ b/doc/bugs/no_way_to_disable_repository_auto_upgrade/comment_4_7ea295a6c113ea0cc3e4e5ae28769190._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2021-02-22T16:35:40Z" + content=""" +Yeah, that command you say you ran makes no sense. + +Now, running that command *does* upgrade the repo, if +upgrading has not already been disabled in the git config. +Because git-annex auto-upgrades on the first command run, +and the fact that the command just errors out due to being +used incorrectly doesn't prevent that from happening. + +But I get the feeling that command is not what you actually did? + +You can run `git config --global annex.autoupgraderepository false` +and you only have to set it that one time for that machine and it will +avoid all upgrades. +"""]]