move to todo

2 files changed, 0 insertions, 37 deletions

diff --git a/doc/bugs/unwanted_repository_version_upgrades.mdwn b/doc/bugs/unwanted_repository_version_upgrades.mdwn
deleted file mode 100644
index 189550803..000000000
--- a/doc/bugs/unwanted_repository_version_upgrades.mdwn
+++ /dev/null
@@ -1,25 +0,0 @@
-Is it possible to freeze or peg repositories at a particular version, or to prevent automatic repository version upgrades?  Is it possible to "downgrade" a repository?
-
-### Please describe the problem.
-
-We have a number of repositories on a shared file server.  These repositories are accessed by multiple machines.  Some of these repositories appear to have gotten upgraded and are now unusable on machines running older versions of git-annex.
-
-We're getting this message:
-[[!format sh """
-user@system:/path/to/repository$ git annex status
-git-annex: Repository version 5 is not supported. Upgrade git-annex.
-"""]]
-
-The machine experiencing the problem is running Debian Wheezy (Stable).
-[[!format sh """
-user@system:/path/to/repository$ git version
-git version 1.7.10.4
-user@system:/path/to/repository$ git annex version
-git-annex version: 3.20120629
-local repository version: 5
-default repository version: 3
-supported repository versions: 3
-upgrade supported from repository versions: 0 1 2
-"""]]
-
-I'm guessing that one of the machines with access to this repository was running a newer version of git-annex, and that the repository was upgraded in the course of some action.
diff --git a/doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment b/doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment
deleted file mode 100644
index 2eee18f1a..000000000
--- a/doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="108.236.230.124"
- subject="comment 1"
- date="2014-06-04T18:14:19Z"
- content="""
-If your repository is not using direct mode, it's completely safe to edit .git/config and set the version back to 3. There is no change between 3 and 5 for indirect mode repositories.
-
-Unfortunately, using git-annex version 5 will automatically upgrade the repository to 5 again. In general, I only want git-annex to support one version at a time, to avoid complicating the code. I did try leaving the indirect mode repositories at v3, but that didn't work out (some details in [[!commit b1d7474c1d713a5b422948178abb4e5f39e85096]]).
-
-I kind of think that part of the problem is that you're using git-annex repositories accessed via a file server. If your server had git-annex installed on it and the clients talked to it only by sshing in and running git-annex-shell, it would not matter if the clients had a newer version, because they'd never access the central repository directly.
-"""]]