From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 18 Jun 2013 14:35:12 GMT
Subject: Re: [PATCH] Documentation/git-push.txt: explain better cases where --force is dangerous
Message-ID: <7v1u7za3mn.fsf@alter.siamese.dyndns.org>
In-Reply-To: <vpq38sfx3ty.fsf@anie.imag.fr>

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>
>> After I re-read the one, I found that "override" somewhat a strange
>> expression.  There is nothing that overrides or to be overriden.
>
> Right, I actually meant "overwrite".
>
>> How about putting it like this?
>
> I'm not sure "push out refs other than the current branch" is strong
> enough. Once you are used to "push = fast-forward = can't loose data",
> "push out a ref" is not very scary.
>
> I'd do s/push out/overwrite/, but I'm fine with your version too.

OK, I agree that it makes sense to do that substitution.
Will queue.