list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <>
To: Junio C Hamano <>
Cc: Git <>
Subject: Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco
Date: Fri, 20 Nov 2020 14:14:26 -0500
Message-ID: <20201120191426.jzaiq42mmlocmd6y@chatter.i7.local> (raw)
In-Reply-To: <>

On Thu, Nov 19, 2020 at 01:25:27PM -0800, Junio C Hamano wrote:
> The question most useful to ask at this point are to what name
> (fixed? computed?) and what the transition plan would look like.

Right, hence my statement that there are no "concrete plans." I've 
previously suggested that, should this change be implemented, it makes 
sense to couple it with another upcoming major compatibility break -- 
the sha1 deprecation. Perhaps we can start with the following:


$ git init
Initialized empty Git repository in /var/home/user/foo/.git/


$ git init
Initialized empty Git repository in /var/home/user/foo/.git/
 Initial branch: master
  Object format: sha1

Use --initial-branch and --object-format flags to specify other values.

> > It is misleading in the context of git, because it implies that a 
> > branch carrying that name is in some way special compared to other 
> > branches (e.g. like "trunk" in the SVN world). In reality, the 
> > "master" branch is just a branch like all others (and can be missing 
> > entirely or have junk in it), so it really shouldn't be called 
> > "master".
> I find the above answer even more confusing, in the context of major
> projects and hosting sites all moving to 'main'.  If 'master' is
> misleading for all the reasons stated in the above paragraph, 'main'
> would equally be misleading.  In other words, "It is just a branch
> like all others, so it really shouldn't be 'master'" leads to "it
> shouldn't be 'main' or 'primary', either".

In my mind, there are important semantic differences between "main" and 
"master" that make "main" more acceptable. A town with a single road can 
reasonably call it the "main road." Similarly, a "mainstream" movement 
does not imply the existence of any other movements. Etc.


  parent reply	other threads:[~2020-11-20 20:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  0:04 Felipe Contreras
2020-11-13  1:01 ` brian m. carlson
2020-11-13  4:27   ` Felipe Contreras
2020-11-13  5:14     ` Theodore Y. Ts'o
2020-11-13  6:28       ` Felipe Contreras
2020-11-13 14:58         ` Theodore Y. Ts'o
2020-11-13 15:37           ` Felipe Contreras
2020-11-13 16:08           ` Michal Suchánek
2020-11-14 14:19           ` Lukasz Niemier
2020-11-15  3:46             ` Theodore Y. Ts'o
2020-11-15  4:27               ` Felipe Contreras
2020-11-19  1:02               ` Brandon Casey
2020-11-19  4:16                 ` Peter Hadlaw
2020-11-19 13:37                 ` Konstantin Ryabitsev
2020-11-19 21:25                   ` Junio C Hamano
2020-11-19 23:29                     ` Felipe Contreras
2020-11-20 19:14                     ` Konstantin Ryabitsev [this message]
2020-11-19 21:29                   ` Brandon Casey
2020-11-20  0:34                     ` Felipe Contreras
2020-11-13  6:09     ` Don Goodman-Wilson
     [not found]     ` <>
2020-11-13  6:47       ` Felipe Contreras
2020-11-13 13:53         ` Philippe Blain
2020-11-13 15:49           ` Felipe Contreras
2020-11-23 15:39           ` Whinis
2020-11-20 18:38     ` Ismael Luceno

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:

  List information:

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

  git send-email \
    --in-reply-to=20201120191426.jzaiq42mmlocmd6y@chatter.i7.local \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone