response

1 files changed, 20 insertions, 0 deletions

diff --git a/doc/forum/Remote_listed_in_whereis_but_not_in_info/comment_1_85cc355213f894e8c1aeece432de67c3._comment b/doc/forum/Remote_listed_in_whereis_but_not_in_info/comment_1_85cc355213f894e8c1aeece432de67c3._comment
new file mode 100644
index 000000000..1db8b0c19
--- /dev/null
+++ b/doc/forum/Remote_listed_in_whereis_but_not_in_info/comment_1_85cc355213f894e8c1aeece432de67c3._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-11-07T18:05:49Z"
+ content="""
+For this to happen, the repository must somehow not be listed in uuid.log,
+but the location log for the file includes its uuid. Normally, any time a
+git-annex repo is initialized, it gets recorded in uuid.log.
+
+One way that could have happened is if `git annex reinit` was run
+with some uuid that was not known in uuid.log. Or, if `git config
+annex.uuid` were manually set.
+
+I don't think it's a problem, other than you not knowing where this
+repository is -- unless some file is only present in that repository. 
+
+You can run `git annex dead` with the uuid as a parameter to mark it dead,
+or you could `git annex describe` with the uuid as a parameter to give
+it a description.
+"""]]