Re: git push default behaviour?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marc Branchaud <marcnarc@xxxxxxxxxxx> writes:

> I agree with Jeremy that the default is dangerous, or at the very
> least surprising.

Yes, --force is not the only problem. Getting constant non-fast forward
errors just because you have out-of-date local ref is annoying, and
really, really confusing.

'push.default = matching' is never a good idea if you use shared
repository actually. It makes sense for people like Junio pushing a
local repository to a public one, which is read-only for the rest of the
world. But my experience is that people using such workflow are advanced
users, and would know how to configure Git, so it wouldn't really harm
them to change the default.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]