git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Felipe Contreras <felipe.contreras@gmail.com>, Ryan <rmrmail@gmx.com>
Cc: git@vger.kernel.org
Subject: Re: "master" term - no one cares
Date: Sat, 13 Aug 2022 17:55:51 +0100	[thread overview]
Message-ID: <0dddb367-ebf9-930f-1b9c-000a532774d3@iee.email> (raw)
In-Reply-To: <CAMP44s2A7nJDVRPbixPPPtTedg_Q53CEdw+sBpGZwOfQG4EZSg@mail.gmail.com>

On 13/08/2022 04:15, Felipe Contreras wrote:
> On Fri, Aug 12, 2022 at 10:10 PM Ryan <rmrmail@gmx.com> wrote:
>> I installed the windows version of git today and was annoyed with the “woke” message stating that the “master” branch term will be changed to a different name to be more “inclusive".
>>
>> Don’t waste your time, just get rid of this annoying woke question in your installer.  Very annoying!!  No one thinks git has anything to do with slavery.  On the plus side, git is great, I just started learning it.  Thanks!
> This is not a Git issue, this is a Git for Windows[1] issue: they are
> the ones exposing that message to their users at installation time.
>
> You can raise the issue in their issue tracker [2], but I wouldn't
> hold my breath.
>
> [1] https://gitforwindows.org/
> [2] https://github.com/git-for-windows/git/issues
>
Thanks for the comment. The wider point is to ensure that everyone can 
choose their own name for their primary line of development (plod), no 
matter how fast or slow they plod along.

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'.

The previous discussion include that of [1], in which I reference the 
paper (it's [4]) regarding the chronometer (clock) .

--
Philip

[1] 
https://lore.kernel.org/git/4bbc8658-4dad-10ef-65a4-8f0f4f4fffd4@iee.email/

  reply	other threads:[~2022-08-13 16:56 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 [this message]
2022-08-14  2:05     ` Felipe Contreras
2022-08-14  8:26       ` demerphq
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=0dddb367-ebf9-930f-1b9c-000a532774d3@iee.email \
    --to=philipoakley@iee.email \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --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).