Re:New GitHub repos to have default branches named “main” in...
by jakelazaroff on Sunday September 20, 2020 @02:19AM
(#24532259)
That is not why it’s called that: https://mail.gnome.org/archives/desktop-devel-list/2019-May/...
[ Parent
| on HN ]
Re:New GitHub repos to have default branches named “main” in...
by ewanm89 on Sunday September 20, 2020 @04:50AM
(#24532775)
Ah, there is a logical fallacy there. That logical fallacy that is just because they reused the same bitkeeper word that they took it from there AND are using it in the same sense. Ultimately this is a strawman, you are putting Bitkeeper's practice and arguments onto git.
Slave is never used once in git documentation, never has been and never will be: https://git-scm.com/search/results?search=slave
Re:New GitHub repos to have default branches named “main” in...
by jakelazaroff on Sunday September 20, 2020 @09:38AM
(#24533960)
That’s fair, but the OP’s conclusion had no supporting premises at all.
Ultimately this is a digression; this change is being made not because of the intentions of the authors of git, but to be considerate of users of GitHub.
Re:New GitHub repos to have default branches named “main” in...
by ballenf on Sunday September 20, 2020 @12:33PM
(#24534957)
> to be considerate of users of GitHub
Which users?
Re:New GitHub repos to have default branches named “main” in...
by throwaway123999 on Saturday October 03, 2020 @04:25AM
(#24670491)
Wrong, it was indeed from "master recording": https://twitter.com/xpasky/status/1272280760280637441
That tweet is from the original creator who made "master" the default branch in git.