On Mon, 28 Mar 2016 14:44:20 -0700
Junio C Hamano wrote:
> Stefan Tauner writes:
>
> The pre-push hook is not the only thing that may prevent you from
> pushing a ref update. As you noticed, non-fast-forward check may
> trigger and decide that a ref is not going to be pushed, and that
> may ha
On Mon, Mar 28, 2016 at 2:44 PM, Junio C Hamano wrote:
> Stefan Tauner writes:
>
>> I noticed that without an additional --force the pre-push hook does not
>> get any input on stdin if a push would result in non-fast-forward
>> uploads. This is not a problem per se (although I don't get the
>> ra
Stefan Tauner writes:
> I noticed that without an additional --force the pre-push hook does not
> get any input on stdin if a push would result in non-fast-forward
> uploads. This is not a problem per se (although I don't get the
> rationale) but it is undocumented and the latter left me puzzled.
Hi,
I noticed that without an additional --force the pre-push hook does not
get any input on stdin if a push would result in non-fast-forward
uploads. This is not a problem per se (although I don't get the
rationale) but it is undocumented and the latter left me puzzled.
(Please keep me in CC sin
4 matches
Mail list logo
