summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-09-15 11:59:24 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-09-15 11:59:24 -0400
commit86fbd93af28ebe85ffd165701e74e2ed8d944b47 (patch)
tree193af43b13a41087c1199d5eab09adce3cdff500
parent9fef3976335acbeeef12e3b8d12d28117779127f (diff)
comment
-rw-r--r--doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_1_babea9a16f25b471026732ea63dd78a8._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_1_babea9a16f25b471026732ea63dd78a8._comment b/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_1_babea9a16f25b471026732ea63dd78a8._comment
new file mode 100644
index 000000000..437613ee7
--- /dev/null
+++ b/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_1_babea9a16f25b471026732ea63dd78a8._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-09-15T15:56:46Z"
+ content="""
+"You may need to force git to push the branch to any git repositories not
+running git-annex." -- git-annex-forget man page
+
+I guess bitbucket doesn't accept pushes that replace an existing branch
+with one with a disconnected history. git push --force should sort it out.
+
+I'm not clear how this is a bug. Is there some change needed in the
+documentation or perhaps in git-annex sync?
+"""]]