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 20:11:01 +0300	[thread overview]
Message-ID: <20200616171048.GA18874@legohost> (raw)
In-Reply-To: <20200616160005.GB667151@coredump.intra.peff.net>

On Tue, Jun 16, 2020 at 12:00:05PM -0400, Jeff King wrote:
> On Tue, Jun 16, 2020 at 05:52:52PM +0300, Oleg wrote:
> > Jeff, where do you get your statistics? github, for example, have around
> > 100 million repos. How many of them want to do it?
> 
> Not statistics, but anecdotally, many major projects and communities
> have expressed interest in switching. Some of them are listed here:
> 
>   https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/

This is not "many", Jeff :-D. There is info just about *few* major projects
(i counted not more than *15*!), that also politically biased and are
intimidated.

> I don't think 100 million is the right number to think about. Many of
> those aren't active, or aren't collaborative. A project like Chrome
> changing their branch name has a much bigger impact than somebody's
> homework repo with three commits.

Jeff, this is a discrimination ;-). And no. This isn't right. How many
repos on github is inactive? May be 20 millions? Add to 80 millions gitlab and
all another git repos from the world. I think we can easily collect around
150-200 million of active repos. Do you really think that count of developers of
these all projects be less than count of Chrome developers? Why do 15 projects
(politically biased) outweighs 200 millions of projects? Is this example of
democracy or rationale mind? May be some there is corruption :-)?

> I was curious about some raw numbers, though, so I picked a random
> sample of ~25k GitHub repositories that had been pushed to in the last
> 30 days.  About 6% have a default branch name besides "master". There's

I think if you get repos from, for example, february instead of *last* 30 days,
then you will get a yet little numbers. Because the last 21 days people are
insane, if you understand me.

And even so - 6% :-D. Jeff, this is really needed thing! :-D
This small numbers show just about one thing - this is useless feature.
Of course, i talk about normal people. In any time, there are a few "not
ordinary" persons and jokers.

> But it seems to me that with 6% non-master names, most tools are going
> to run into these cases sooner or later, and have to deal with it. I'd
> be much more worried about one-off scripts that see a small, non-uniform
> set of repositories.

Look, now this is a problem of rare "geniuses". Why do you want to bring
these problems to all of us :-)? What did we do you?

> I think it's clear that this _is_ a politically-driven change. It is not
> helping the software in any technical way to change the name. The

Yes. You are absolutely right.

> question is whether the more abstract benefits to people are worth the
> potential costs.

Of course, not. This is obvious.

> But I don't think anybody has been able to quantify the benefits in a
> meaningful way. Or at least a way that everyone agrees on.

Jeff, everything is simpler. You lie to youself about it :-). *Everybody*
adequate person will say you that there are *no* benefits at all. Only
troubles, troubles and troubles. And we are already seeing this. There is no
need for a time machine. This will helps nobody. This changes willn't materialize
food for homeless and willn't protect someone from humiliation. But in current time,
when people click "like" button instead of doing real things for others and think
that they do "everything right" and this helps somebody :-), this is hard to
understand. If you would find any slave which is offended by
"master" word, then this conversation was meaningful. But now it looks like
people who have never been masters appologize to people who have never been
slaves. And are doing this, note please, in very strange manner.

Look, if you really try to make somebody life better, just image that you
have no access to git code. How can you help? Search the better way that
will really helps somebody. Don't break git. And after several monthes,
when common sense will return to us, we will look again on this "useful"
change.

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

  reply	other threads:[~2020-06-16 17:09 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
2020-06-16 16:00       ` Jeff King
2020-06-16 17:11         ` Oleg [this message]
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=20200616171048.GA18874@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).