On Wed, Aug 20, 2014 at 12:06 AM, Junio C Hamano [off-list ref] wrote:
The basic flow based on this mechanism goes like this:
1. You push out your work with "git push -s".
2. The sending side learns where the remote refs are as usual,
together with what protocol extension the receiving end
supports. If the receiving end does not advertise the protocol
extension "push-cert", the sending side falls back to the normal
push that is not signed.
Is this fallback silently? If so I think it would be better to abort
the push, if the receiver does not support this but the user requested
it.
Bert