git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Oleg <lego_12239@rambler.ru>
To: git@vger.kernel.org
Subject: Re: Consensus on a new default branch name
Date: Tue, 16 Jun 2020 17:52:52 +0300	[thread overview]
Message-ID: <20200616145207.GA13998@legohost> (raw)
In-Reply-To: <20200616143107.GL666057@coredump.intra.peff.net>

On Tue, Jun 16, 2020 at 10:31:07AM -0400, Jeff King wrote:
> stopping at configurability is the least risky thing there. But it's
> clear that a lot of projects are interested in changing their names, so

Jeff, where do you get your statistics? github, for example, have around
100 million repos. How many of them want to do it?

> > > 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.
> 
> My opinion is that "main" is the best suggestion I've heard.

I have a better suggestion, imho. Let's make "master" a default name. Thus:

1. we willn't break utilities and user hopes; this is a backward compatibility.
2. we will see how many projects really need this "feature".

I think backward compatibility is a reasonable and useful thing. And if this is
not a political-driven changes, i see no technical reason to not do so.

-- 
Олег Неманов (Oleg Nemanov)

  reply	other threads:[~2020-06-16 14:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:57 Consensus on a new default branch name Taylor Blau
2020-06-15 21:10 ` Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31   ` Jeff King
2020-06-16 14:52     ` Oleg [this message]
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=20200616145207.GA13998@legohost \
    --to=lego_12239@rambler.ru \
    --cc=git@vger.kernel.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.
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).