> I believe I've said something that's easy to understand, at least without bad faith. I’m pretty sure I understand what you’re saying - "this change only affe

> I believe I've said something that's easy to understand, at least without bad faith. I’m pretty sure I understand what you’re saying - "this change only affects creation of new repos”? The responder isn’t missing your point, they’re disagreeing with it - they're pointing out that anybody who needs to work with a repo now needs to explicitly configure the name of the canonical branch, where previously they could safely assume the default was “master”; ergo it affects anybody who uses a repo for as long as it exists, not just the repo creator and not just at repo creation time. > adding changes in a backward-compatible way so that not to change the expected behavior The expected behaviour until recently was that “git checkout master” would take you to the canonical source branch - this behaviour has changed, in a backward-incompatible way (any code which worked in the past by using that command now needs to be changed)