They do use different branch names all the time, e.g. many projects have a development branch or branches for developing new (larger) features, but it’s still useful to have one standardized branch name in each project and especially so for the code that you want to present to the outside.
It’s what GitHub, GitLab, Gitea etc. show by default. It’s what gets checked out when you run “git clone”. It’s just been perfectly clear terminology up until now, for discussing the handling of branches.
And now we’re throwing that all away for really just no reason. I’m not saying that I disagree with the reason, I’m saying there is no reason presented. “Master” is not related to slavery in any way here. And no, calling me a right-wing snowflake is not a reason either, especially since I’m a far-left snowflake.
People use different branches all the time, and non-programmers wouldnt even notice this change if it wasnt for the whining of right-wing snowflakes.
They do use different branch names all the time, e.g. many projects have a development branch or branches for developing new (larger) features, but it’s still useful to have one standardized branch name in each project and especially so for the code that you want to present to the outside.
It’s what GitHub, GitLab, Gitea etc. show by default. It’s what gets checked out when you run “git clone”. It’s just been perfectly clear terminology up until now, for discussing the handling of branches.
And now we’re throwing that all away for really just no reason. I’m not saying that I disagree with the reason, I’m saying there is no reason presented. “Master” is not related to slavery in any way here. And no, calling me a right-wing snowflake is not a reason either, especially since I’m a far-left snowflake.
According to this it actually is a reference to slavery.
https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html