Hi, Since a few days we have a very strange problem with our (bare) central git repo. Every night some refs in refs/heads get reset to older CSs. It is not clear why that happens. The repo has the config 'receive.denyNonFastForwards = true' so it cannot be due to a push to the central repo, right? I also don't think that someone does a 'git reset' or something directly on the central repo. Today it happened again and luckily no new changes were pushed to the central repo after the event so I inspected the files in refs/heads. The modification time and owner of the "tampered" refs seam to indicate that it was a cron job that changed them. The cron job does a 'git --git-dir=<path_to_central_repo> push foo' to update a remote repo 'foo' which was added to the central repo with 'git remote add --mirror foo ssh://<host>/<path_to_foo>'. This setup was working well for quite a while. Is it possible that the 'git push' changes refs in the central repo, i.e. the 'from' repo? Another interesting information might be that I now also get an email from the cron job every night: yp_all: clnt_call: RPC: Unable to receive; errno = Connection reset by peer That started at the same night I first saw the reset of the refs. I now replaced that cron job with another one running on the remote host that does a ''git remote update --prune" on the remote repo. Hopefully that resolves the problem. Any feedback on what might be going on is highly appreciated. Oh, the OS is Linux (RHEL4.8) and the git version is 1.7.0 Thanks in advance, Peter -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html