Stefan Beller <[email protected]> writes: > Although 1.8..2.8 is a lot, Git ought to stay compatible there.
In principle that is true, but there were deliberate backward incompatible changes at around 2.0 boundary, and those who followed along the upgrade paths were given warnings and advice messages to guide them to adjust their configurations during the incremental upgrade path. It is not all that surprising if somebody who jumped between the two versions in one hop didn't benefit from any such guidance, though. Offhand, perhaps .git/config left by ancient versions and recent versions may differ in such a way that it affects the particular workflow deployed there? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
