diff options
author | 2015-09-15 13:38:09 -0400 | |
---|---|---|
committer | 2015-09-15 13:38:09 -0400 | |
commit | 2dadeb70f4132371c9332e3f84b1350778bedeb6 (patch) | |
tree | 77d0198606f032b25444cf220219492435f08911 | |
parent | bb025fc0e068552623b995976d0449f816eb30ba (diff) |
comment
-rw-r--r-- | doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment b/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment new file mode 100644 index 000000000..be0e49094 --- /dev/null +++ b/doc/bugs/git-annex_branch_not_being_pushed_after_git-annex_forget/comment_3_70f2b9e61e90528fdbef4d8a6e8dd972._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-09-15T17:34:15Z" + content=""" +What git-annex command? + +`git-annex sync` should already deal with this, AFAICS. It forces the push +to the remote's synced/git-annex branch. + +Some remote's may have receive.denyNonFastForwards set, which will prevent +even a forced push. git-annex sync prints out some hints if this happens. +"""]] |