From a7fcda861fdd3318d41ff6495312273947917b7f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 10 Jul 2020 16:09:13 -0400 Subject: [PATCH] comment --- ..._804ecf5218ce147767352fea8ea5eae8._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/bugs/new_repo_with_git-lfs_as_only_annex_remote/comment_1_804ecf5218ce147767352fea8ea5eae8._comment diff --git a/doc/bugs/new_repo_with_git-lfs_as_only_annex_remote/comment_1_804ecf5218ce147767352fea8ea5eae8._comment b/doc/bugs/new_repo_with_git-lfs_as_only_annex_remote/comment_1_804ecf5218ce147767352fea8ea5eae8._comment new file mode 100644 index 0000000000..67f7252d1e --- /dev/null +++ b/doc/bugs/new_repo_with_git-lfs_as_only_annex_remote/comment_1_804ecf5218ce147767352fea8ea5eae8._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-07-10T20:05:09Z" + content=""" +It seems to me there are two possible mistakes you could have made, both +of which are much more likely than a bug in git-annex. They are: + +1. You forgot to push the git-annex branch to origin, so your clone was not + able to see it. + +2. When you say you "set up the same git-lfs special remote" again, + you mean you used `git-annex initremote` again. Which sets up a + *different* remote with a different uuid. The right thing to do would be + to use `git annex enableremote`. (Or indeed to get git-annex + auto-enable the git-lfs special remote when it sees you cloned the same + url that was used to set it up) + +If you still think you have a bug, you'll need to show me a list of +commands that I can use to reproduce the bug. +"""]]