Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH] Documentation/git-push.txt: explain better cases where --force is dangerous

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:57:48

Matthieu Moy [off-list ref] writes:
Junio C Hamano [off-list ref] writes:

quoted
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".
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help