list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: "brian m. carlson" <>
To: Felipe Contreras <>
Cc: Git <>, Junio C Hamano <>,
	Johannes Schindelin <>,
	Don Goodman-Wilson <>
Subject: Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco
Date: Fri, 13 Nov 2020 01:01:07 +0000
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

On 2020-11-13 at 00:04:23, Felipe Contreras wrote:
> *If* we are going to rename the master branch, it should be with a
> good reason, after discussing it appropriately, in a major release
> (i.e. Git 3.0), after a period of deprecation, and a big warning to
> invite users to provide feedback about the important upcoming change.
> We can hedge these types of changes with a "core.mode=next"
> configuration, as I argued back in 2013. [3]

When the original email that proposed this change came up, I did suggest
that this would be suitable for a Git 3.0.  I think such a version
number bump would be valuable, but I know that Git doesn't follow
semantic versioning and I'm happy for Junio to make the call.  Git has
made incompatible changes in the past in non-major versions, so there is
precedent for this, although I agree it has the potential to be
surprising.  Again, I defer to Junio's judgment here.

I should point out that there is an option to test or set this already,
with init.defaultBranch.  I have used this feature for testing in the
past, and I use the feature now to set default branches.  It's also
possible to use the template functionality to set a default branch name
for new repositories and I've tested support for this back to at least
Git 2.0 (but I believe it goes back even farther).  And, of course,
either of these options can be used for developers to choose the branch
name which meets the needs of the project best.

As for consultation with users, there was a discussion about this on the
list a few months back and we did get a lot of input from various
parties.  Some of that feedback was hostile and inappropriate and some
even violated our code of conduct in my view, as is all too common with
potentially controversial topics, and I'm not eager to repeat such a
discussion, since I don't think it's going to result in a productive,
positive outcome.
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2020-11-13  1:02 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 [this message]
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
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 \ \ \ \ \ \ \ \

* 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