From 6f8322b8f72f3399d4c28426749db5d01742001d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 12 Jun 2019 14:45:25 -0400 Subject: [PATCH] close; not a bug --- ..._confuses_git-annex-init_and_git-annex-sync.mdwn | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/bugs/git-clone_--single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn b/doc/bugs/git-clone_--single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn index 734678adba..f5f3f5d9dd 100644 --- a/doc/bugs/git-clone_--single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn +++ b/doc/bugs/git-clone_--single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn @@ -1 +1,14 @@ If a repo is cloned using `git clone --single-branch --depth 1`, `git-annex-init` and `git-annex-sync` do not seem to correctly fetch the `git-annex` and `synced/git-annex` branches. `git-annex-info` does not list remotes that were known at the cloned repo. + +> This is not a bug. You have cloned a repository without cloning the +> git-annex branch, so as far as git-annex can *possibly* know, this is a +> git repository in which git-annex has never been used before. +> +> As soon as you fetch the git-annex branch from origin, git-annex will +> know all the information that you expected it to know. So all you have to +> do is: `git fetch origin git-annex` +> +> There is no possible change I can make that will prevent or amelorate +> this particular means of shooting yourself in the foot. +> +> [[done]] --[[Joey]]