From 68c900f95485e4f63c319cb7435442158bf68d53 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 27 Aug 2025 12:37:07 -0400 Subject: [PATCH] remove para about conflicts That was only ever relevant for the v1 upgrade! --- doc/upgrades.mdwn | 5 ----- 1 file changed, 5 deletions(-) diff --git a/doc/upgrades.mdwn b/doc/upgrades.mdwn index 7d48547d82..01e0054dfa 100644 --- a/doc/upgrades.mdwn +++ b/doc/upgrades.mdwn @@ -38,11 +38,6 @@ refuse to do anything. To upgrade, use the "git annex upgrade" command. To prevent automatic upgrades in a repository, run: `git config annex.autoupgraderepository false` -The upgrade process is guaranteed to be conflict-free. Unless you -already have git conflicts in your repository or between repositories. -Upgrading a repository with conflicts is not recommended; resolve the -conflicts first before upgrading git-annex. - The upgrade process needs to write to the repository. If the original repository cannot be written to (due to eg being on readonly media), the upgrade would need to be run in a copy of the repository. -- 2.30.2