From d2658d9537843a4f713ca397f233252d0eb53023 Mon Sep 17 00:00:00 2001
From: Ilya_Shlyakhter <Ilya_Shlyakhter@web>
Date: Tue, 11 Jun 2019 23:30:26 +0000
Subject: [PATCH] an issue involving repos cloned with --single-branch

---
 ...single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 doc/bugs/git-clone_--single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn

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
new file mode 100644
index 0000000000..734678adba
--- /dev/null
+++ b/doc/bugs/git-clone_--single-branch_confuses_git-annex-init_and_git-annex-sync.mdwn
@@ -0,0 +1 @@
+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.