git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>,
	James Ramsay <jramsay.com.au@syl.local>,
	Bryan Turner <bturner@atlassian.com>
Subject: Consensus on a new default branch name
Date: Mon, 15 Jun 2020 14:57:22 -0600	[thread overview]
Message-ID: <20200615205722.GG71506@syl.local> (raw)

Hello,

Over the past few days or so, there has been significant discussion [1] and
patches [2] about changing the name of the default branch away from 'master' and
towards something else.

Concurrently with this, GitHub, GitLab [3], and Bitbucket are working together
in order to make a similar change across our respective products. Because of
this, we are met with a bit of a challenge: we would like to make these changes
before the next version(s) (and so need to settle on a new default branch name),
but we also want to avoid a situation where the community is fractured (eg.,
GitHub uses 'main', Git uses 'default', etc).

A related question is whether or not we plan to change the default value of
'core.defaultBranchName' at all (once Johannes' patches land, of course). That
seems to be the intent in [4], but forming consensus around this would be good,
too.

So, I would like to form some consensus here as to what the new name should be,
if that is something we're committing to doing. This way, we can make this
decision now (and allow hosts to make their corresponding changes) while still
giving us on the list some time to work on the implementation across one or
more release boundaries.

My interpretation thus far is that 'main' is the planned replacement for
'master'. Consensus seems to have formed around this name [5], but if that's
incorrect--or there are yet-unvoiced opinions that you would like to share--now
is the time to discuss further.

Thanks,
Taylor

[1]: https://lore.kernel.org/git/CAOAHyQwyXC1Z3v7BZAC+Bq6JBaM7FvBenA-1fcqeDV==apdWDg@mail.gmail.com/
[2]: https://lore.kernel.org/git/pull.656.v2.git.1592225416.gitgitgadget@gmail.com/
[3]: https://gitlab.com/gitlab-org/gitlab/-/issues/222204
[4]: https://lore.kernel.org/git/nycvar.QRO.7.76.6.2006111610000.56@tvgsbejvaqbjf.bet/
[5]: https://lore.kernel.org/git/nycvar.QRO.7.76.6.2006091126540.482@ZVAVAG-DN14RQO.ybpnyqbznva/

             reply	other threads:[~2020-06-15 20:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:57 Taylor Blau [this message]
2020-06-15 21:10 ` Consensus on a new default branch name Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31   ` Jeff King
2020-06-16 14:52     ` Oleg
2020-06-16 16:00       ` Jeff King
2020-06-16 17:11         ` Oleg
2020-06-16 17:32           ` Konstantin Ryabitsev
2020-06-16 18:54             ` Oleg
2020-06-16 22:18           ` Jeff King
2020-06-16 16:10     ` Konstantin Ryabitsev
2020-06-16 16:13       ` Santiago Torres Arias
2020-06-16 16:48         ` Jeff King
2020-06-16 16:14       ` Jason Pyeron
2020-06-16 16:47       ` Jeff King
2020-06-16 17:44       ` Steve Litt
2020-06-16 19:00         ` Oleg
2020-06-17 18:06     ` Michal Suchánek
2020-07-01 17:31       ` Michal Suchánek
2020-07-01 21:57         ` Jeff King
2020-07-02 12:21           ` Whinis
2020-07-02 21:15             ` Philip Oakley
2020-07-02 21:59               ` Whinis
2020-07-02 22:47                 ` Philip Oakley
2020-07-02 23:08                   ` Whinis
2020-07-01 22:25         ` Jonathan Nieder
2020-06-15 22:38 ` Elijah Newren
2020-06-16 14:32   ` Jeff King
2020-06-17 20:13     ` Junio C Hamano
2020-06-15 23:24 ` brian m. carlson
2020-06-16  0:50 ` James Ramsay
  -- strict thread matches above, loose matches on Subject: below --
2020-06-16  1:58 Nomen Nescio
2020-06-16  2:22 ` Jonathan Nieder
2020-06-16  2:31   ` Taylor Blau
2020-06-16 14:38   ` Jeff King
2020-06-17  0:01 Anonymous Remailer (austria)

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=20200615205722.GG71506@syl.local \
    --to=me@ttaylorr.com \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=jramsay.com.au@syl.local \
    --cc=peff@peff.net \
    /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).