Disable receive.denyNonFastForwards when setting up a gcrypt special remote
gcrypt needs to be able to fast-forward the master branch. If a git repository is set up with git init --shared --bare, it gets that set, and pushing to it will then fail, even when it's up-to-date.
This commit is contained in:
parent
0ddf4d3148
commit
1536ebfe47
3 changed files with 27 additions and 13 deletions
2
debian/changelog
vendored
2
debian/changelog
vendored
|
@ -28,6 +28,8 @@ git-annex (4.20130921) UNRELEASED; urgency=low
|
|||
written by MacGPG.
|
||||
* assistant: More robust inotify handling; avoid crashing if a directory
|
||||
cannot be read.
|
||||
* Disable receive.denyNonFastForwards when setting up a gcrypt special
|
||||
remote, since gcrypt needs to be able to fast-forward the master branch.
|
||||
|
||||
-- Joey Hess <joeyh@debian.org> Sun, 22 Sep 2013 19:42:29 -0400
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue