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

Re: [RFD] Making "git push [--force/--delete]" safer?

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

Johannes Sixt [off-list ref] writes:
Am 7/3/2013 21:53, schrieb Junio C Hamano:
quoted
Johannes Sixt [off-list ref] writes:
quoted
I don't think that is necessary. We already have *two* options to
force-push a ref: the + in front of refspec, and --force.
They mean exactly the same thing; the only difference being that "+"
prefix is per target ref, while "--force" covers everything, acting
as a mere short-hand to add "+" to everything you push.
I know, and I'm saying that we do not have to keep this duplicity.
Of course we do.  If you change + prefix to "push but always require
tracking ref in the opposite direction", you will break existing
setup by (1) making it impossible to loosen the restriction per ref,
and (2) forcing people to have reverse tracking ref.

It is OK to introduce another prefix that mean a new thing.  It is
absolutely not OK to change the semantics of only one and not the
other.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help