From bf6557b4e80b88f9c5e219c8a7d63ef5730bfb93 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 29 Jan 2021 14:24:52 -0400 Subject: [PATCH] close --- ...pository_is_known_to_contain_the_file__34___after_sync.mdwn | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/bugs/fsck_is_required_to_resolve___34__no_other_repository_is_known_to_contain_the_file__34___after_sync.mdwn b/doc/bugs/fsck_is_required_to_resolve___34__no_other_repository_is_known_to_contain_the_file__34___after_sync.mdwn index b92c995d35..1248dcd80c 100644 --- a/doc/bugs/fsck_is_required_to_resolve___34__no_other_repository_is_known_to_contain_the_file__34___after_sync.mdwn +++ b/doc/bugs/fsck_is_required_to_resolve___34__no_other_repository_is_known_to_contain_the_file__34___after_sync.mdwn @@ -17,3 +17,6 @@ Does this seem like a bug with git annex? Is there a possible gap in the way tha ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Git annex works for us the majority of the time and solves a lot of space issues for us in a unique way. We do get confused by it sometimes, but that's probably our implementation of it and not knowing enough about it across our team (seems to be a set and forget approach). + +> Closing as it's not clear this was a bug rather than user error as +> explained in my comment. [[done]] --[[Joey]] -- 2.30.2