mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
http://alan.petitepomme.net/ 2013-10-23 16:21:31 +00:00 • committed by admin
parent 726466da61
commit cda10807e4
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="http://alan.petitepomme.net/"
nickname="Alan Schmitt"
subject="comment 2"
date="2013-10-23T16:21:30Z"
content="""
I think I found the problem, after much googling.
The command line you suggest is indeed tried, and rejected by the server.
The answer came from [here](http://stackoverflow.com/questions/253055/how-do-i-push-amended-commit-to-the-remote-git-repo) where it says (speaking of a forced push)
> Even this may not work as git allows remote repositories to refuse non-fastforward pushes at the far end by using the config variable 'receive.denynonfastforwards'.
Indeed this is set in my annex repository. Note that this is a local setting, and that repository was created by the assistant.
I removed this setting, and I can now push. Could the setting of this bit be a bug in the assistant?
In any case, thanks a lot for indicating where to look at.
"""]]