unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: generating a git repo: main instead of master
Date: Sun, 13 Nov 2022 12:31:31 +0300	[thread overview]
Message-ID: <Y3C5czyXKRoJpigR@protected.localdomain> (raw)
In-Reply-To: <87leofe0xe.fsf@mat.ucm.es>

* Uwe Brauer <oub@mat.ucm.es> [2022-11-13 11:05]:
> It seems that more and more public repositories expect that the
> principal git branch should be «main» instead of «master»

master has many definitions:

* Overview of noun master

The noun master has 10 senses (first 6 from tagged texts)
1. (8) maestro, master -- (an artist of consummate skill; "a master of the violin"; "one of the old masters")
2. (5) overlord, master, lord -- (a person who has general authority over others)
3. (1) victor, master, superior -- (a combatant who is able to defeat rivals)
4. (1) master -- (directs the work of others)
5. (1) headmaster, schoolmaster, master -- (presiding officer of a school)
6. (1) master, master copy, original -- (an original creation (i.e., an audio recording) from which copies can be made)
7. master, captain, sea captain, skipper -- (an officer who is licensed to command a merchant ship)
8. master -- (someone who holds a master's degree from academic institution)
9. master, professional -- (an authority qualified to teach apprentices)
10. passkey, passe-partout, master key, master -- (key that secures entrance everywhere)

So when we use "master" in git repositories, the definition number
6. applies, as in "master copy".

For everybody's attention, the definition "master" in git does not
apply to any living person who has general authority over others.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



      parent reply	other threads:[~2022-11-13  9:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13  8:03 generating a git repo: main instead of master Uwe Brauer
2022-11-13  8:24 ` Eli Zaretskii
2022-11-13  8:25   ` Eli Zaretskii
2022-11-13  8:38   ` Uwe Brauer
2022-11-13  9:27     ` tomas
2022-11-13 14:50     ` Björn Bidar
2022-11-13  8:26 ` Peter Hardy
2022-11-13  8:32 ` Teemu Likonen
2022-11-13  8:33 ` tomas
2022-11-13  8:43   ` Uwe Brauer
2022-11-13  9:22     ` tomas
2022-11-13  9:31 ` Jean Louis [this message]

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: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=Y3C5czyXKRoJpigR@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).