]> dgit.raspbian.org Git - git-annex.git/commitdiff
comment
authorJoey Hess <joeyh@joeyh.name>
Mon, 8 Nov 2021 20:28:43 +0000 (16:28 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 8 Nov 2021 20:28:43 +0000 (16:28 -0400)
doc/bugs/uninit_errors_out_on_repo_without_commits/comment_1_3c834367176581732e38d0b3f7f86a40._comment [new file with mode: 0644]

diff --git a/doc/bugs/uninit_errors_out_on_repo_without_commits/comment_1_3c834367176581732e38d0b3f7f86a40._comment b/doc/bugs/uninit_errors_out_on_repo_without_commits/comment_1_3c834367176581732e38d0b3f7f86a40._comment
new file mode 100644 (file)
index 0000000..40ea46f
--- /dev/null
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2021-11-08T20:24:15Z"
+ content="""
+It seems that not only does your repository not
+have any commits in master, it also lacks a git-annex branch.
+
+Since `git-annex init` creates the git-annex branch, and git will
+refuse to clone a repo with no master branch, I don't know how you
+could have gotten a repo in this state. 
+(Aside from manually deleting the branch first.)
+
+With a git-annex branch, I see only the unknown HEAD warning,
+but it does succeed.
+"""]]