git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: demerphq <demerphq@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Philip Oakley <philipoakley@iee.email>, Ryan <rmrmail@gmx.com>,
	Git <git@vger.kernel.org>
Subject: Re: "master" term - no one cares
Date: Sun, 14 Aug 2022 10:26:21 +0200	[thread overview]
Message-ID: <CANgJU+U_xgghdX58XsAY7dNUj1dE8STviTAL0ygycnAesZ+VxQ@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s1XOyMgX+4hHzNXpUmJ0DURn93=B9dH0pBm5Fk5YRfdvg@mail.gmail.com>

On Sun, 14 Aug 2022, 04:35 Felipe Contreras, <felipe.contreras@gmail.com> wrote:
>
> On Sat, Aug 13, 2022 at 11:55 AM Philip Oakley <philipoakley@iee.email> wrote:
> > There is a confusion between the use of the term that refers to the
> > *personal* mastery of a _craft_ or _artisan_ technique and, at least one
> > of, the historical choices for the usage of the term 'master', which was
> > a direct reference to slave servitude. That was for the use of
> > electrical circuits which would detect the 'tick' of a primary timing
> > pendulum and then have all the actual clock faces that indicated the
> > time be _driven_ from that 'master'.
>
> This may be the reason why some people used that name in the past, but
> it's not the reason I use it.
>
> For me if I was cloned there wouldn't be two equally valid versions of
> me, *I* am the original one, I am the "master" copy. This doesn't
> change if my clone is cloned in turn.
>
> This is exactly how master branches in git are used. I have a master
> branch of git.git, but it's not *the* master branch. *The* master
> branch is the branch from which all the other branches came from,
> including "maint" and "next", and all the dozens of branches in
> thousands of other repositories. If the word "master" makes it sound
> more important than all the other branches in all the other
> repositories, it's because it is.
>
> Regardless of what name people use and for what reason, the reality is
> that "master" is still very widely used, despite of the campaign
> against it which was clearly driven by ideological reasons.

FWIW, I was a part of ensuring two large codebases did not use the
term "master" when they migrated to git long before it became a
subject of controversy.  Not because I had concerns over the
master/slave word association (it really wasnt on my mind) but simply
because the word "master" is too overloaded, and its use as a name
leads to all sorts of weird sentences involving the phrase "master
master", which for newbies especially can be really confusing.  I
found that introducing newbies to the concepts of distributed version
control goes much more smoothly when the "primary" branch is not
called "master", as it avoids the need to understand that there are
various different copies of the "master" branch where either only one
or none of them are actually master branches. Just writing this
paragraph makes me itch from having to distinguish the different uses
of the word master.

So while it is indisputable that what you call "ideological reasons"
really pushed this initiative into the public consciousness I think
there were and are a lot of us who are quite happy to support the
movement simply because we think using a word which (in English) has
multiple Noun, Adjective and Verb definitions is a poor choice for the
*name* (Proper Noun) of an arbitrary artifact, especially when those
definitions will likely be applied to thing being named. That the
phrase "master master" is in our vocabulary is a horrorshow. To me it
is not unlike naming someone's two children "Run" and "Slowly". Who is
going to understand what the heck "Run, Slowly, run slowly!" means?

The fact you need to distinguish <"the" master> from other uses of the
word "master" when talking above is to me a clear indication how bad a
name choice it was.  I get it, from certain perspectives, it is an
attractive name, but if you zoom out a bit, it just seems to regularly
lead to unfortunate sentences, at least in English. Try explaining how
the "master" branch is used to someone who knows nothing about tech,
like your Grandmother, or Uncle or something, I bet they are totally
lost within the first sentences. At least if they are English
speakers, other languages may overload the word differently. Dont
forget to explain the difference between "canonical master" like
Linus'es master master, and distinguish it from the various other
"master" branches that would be out there, and how most of them aren't
the master at all.

Anyway, just my $0.02. Thanks for listening.

cheers,
Yves

  reply	other threads:[~2022-08-14  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13  2:57 "master" term - no one cares Ryan
2022-08-13  3:15 ` Felipe Contreras
2022-08-13 16:55   ` Philip Oakley
2022-08-14  2:05     ` Felipe Contreras
2022-08-14  8:26       ` demerphq [this message]
2022-08-14 17:19         ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANgJU+U_xgghdX58XsAY7dNUj1dE8STviTAL0ygycnAesZ+VxQ@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.email \
    --cc=rmrmail@gmx.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).