GitLab has just posted the following re: default branches. https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/ Please take a moment to pause before posting. Please consider whether additional comments are constructive. I'm concerned that rehashing the same arguments will reflect poorly on the Python Core Development community. Thank you. On Wed, Mar 10, 2021 at 4:35 PM Jonathan Cronin <jon@egh.com> wrote:
On Mar 10, 2021, at 4:45 PM, David Mertz <mertz@gnosis.cx> wrote:
In contrast, the "master" used in version control directly borrows from so-called "master/slave network architecture." I saw in this thread one implausible argument that it was intended in the sense of "magister." I don't believe it, but even if we stipulate that whoever first used the word in relation to version control meant that, nearly everyone else who discusses it means "master/slave."
I don't think it derives from "master/slave network architecture.”. I think it derives from the use of “master” to denote an instance or prototype that is used to create identical copies or replicas, a usage that predates networking, as in master tape, master print, and, (perhaps archaically for you :)), mimeograph master.
Irrelevantly, I also think all (almost all?) uses of "master/slave” to describe network architectures are lazy; there is a better existing description, e.g. “active/passive”, “polling” etc.
Jonathan
P.S. My preference would be “mainline” over “main”. I like railroad version diagrams. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/DONBBIFH... Code of Conduct: http://python.org/psf/codeofconduct/