From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 22 Jun 2012 23:59:01 GMT
Subject: Re: Master and origin/master diverged
Message-ID: <7v1ul6nbju.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CAE1pOi2MN_c76UBeRzdRbU8s+0LzYVoVcJ13V0di=HQobj+aDg@mail.gmail.com>

Hilco Wijbenga <hilco.wijbenga@gmail.com> writes:

>> Some ways you can prevent it from happening again:
>> (1) setting your canonical repo config to deny non-ff, and deny deletes:
>> [receive]
>>        denyDeletes = true
>>        denyNonFastforwards = true
>
> I would *really* like to do that but I need access to the server for
> that, right? Unfortunately, we use Unfuddle and that means no such
> access. So no server config changes and no Git hooks.

receive.denyNonFastforwards is a reasonable thing to ask for
projects with a shared repository workflow, so I suspect hosting
service providers may want to race adding support for it to win
customers.  Have you asked them?