git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Oleg <lego_12239@rambler.ru>
To: Git List Mailing <git@vger.kernel.org>
Subject: Re: Avoiding 'master' nomenclature
Date: Fri, 31 Jul 2020 11:19:25 +0300	[thread overview]
Message-ID: <20200731081925.GA5533@legohost> (raw)
In-Reply-To: <20200731005721.GC240563@coredump.intra.peff.net>

On Thu, Jul 30, 2020 at 08:57:21PM -0400, Jeff King wrote:
> On Thu, Jul 30, 2020 at 11:17:43AM +0300, lego_12239@rambler.ru wrote:
> > On Wed, Jul 29, 2020 at 01:38:56PM -0700, Jonathan Nieder wrote:
> > > The commit message describes its intent
> > >   commit 489947cee5095b168cbac111ff7bd1eadbbd90dd
> > >   Author: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> > >   Date:   Tue Jun 23 22:33:23 2020 +0000
> > > 
> > >       fmt-merge-msg: stop treating `master` specially
> > > 
> > >       In the context of many projects renaming their primary branch names away
> > >       from `master`, Git wants to stop treating the `master` branch specially.
> > 
> > Wow. Jonathan, you are a good student of Goebbels! "many projects" :-D.
> > You lie. These are few but very noisy projects. Don't kid youself.
> 
>   - the text you are responding to isn't even Jonathan's; it was a
>     quoted commit message to give context.

Yes. It's my mistake. Sorry.

>   - if you really do want re-open the argument about whether projects
>     are interested in changing branch names, it might help to provide
>     some actual data. Most of the data-less points (on both sides) have
>     already been made in past discussions.

Most of the actual data have already been made, but polytics won out over
common sense.

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

  reply	other threads:[~2020-07-31  8:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 19:44 Avoiding 'master' nomenclature Linus Torvalds
2020-07-29 20:04 ` Junio C Hamano
2020-07-29 20:23   ` Linus Torvalds
2020-07-29 20:38     ` Jonathan Nieder
2020-07-29 20:46       ` Linus Torvalds
2020-07-29 20:56         ` Linus Torvalds
2020-07-30  8:17       ` lego_12239
2020-07-31  0:57         ` Jeff King
2020-07-31  8:19           ` Oleg [this message]
2020-07-29 20:40     ` Linus Torvalds
2020-07-29 20:58       ` Jeff King
2020-07-29 21:20         ` Linus Torvalds
2020-07-30  0:29           ` Jeff King
2020-07-30  0:44             ` Linus Torvalds
2020-07-30  0:52               ` Jeff King
2020-07-30  0:57                 ` Linus Torvalds
2020-07-31  0:44                   ` Jeff King
2020-07-29 21:25         ` Junio C Hamano
2020-07-29 22:50           ` Junio C Hamano
2020-07-30  0:14             ` Jeff King
2020-07-30  0:23               ` Linus Torvalds
2020-07-30 10:11                 ` Michal Suchánek
2020-07-30  0:31               ` Jeff King
2020-07-30  0:36             ` Junio C Hamano
2020-07-30 18:02               ` [PATCH v3 0/2] fmt-merge-msg: selectively suppress "into <branch>" Junio C Hamano
2020-07-30 18:02                 ` [PATCH v3 1/2] Revert "fmt-merge-msg: stop treating `master` specially" Junio C Hamano
2020-07-30 19:10                   ` Eric Sunshine
2020-07-30 19:40                     ` Junio C Hamano
2020-07-30 18:02                 ` [PATCH v3 2/2] fmt-merge-msg: allow merge destination to be omitted again Junio C Hamano
2020-07-31  0:42                 ` [PATCH v3 0/2] fmt-merge-msg: selectively suppress "into <branch>" Jeff King
2020-07-31  2:04                   ` Junio C Hamano
2020-07-31  2:22                     ` Jeff King
2020-07-31 20:03                       ` Taylor Blau
2020-07-31 20:12                         ` Junio C Hamano
2020-07-31 20:17                           ` Taylor Blau
2020-08-01  7:15                         ` Michal Suchánek
2020-08-10 11:53               ` Avoiding 'master' nomenclature Johannes Schindelin
2020-08-10 15:45                 ` Junio C Hamano
2020-08-11  2:39                   ` Johannes Schindelin
2020-08-12  0:30                     ` Junio C Hamano
2020-07-29 20:40     ` Junio C Hamano
2020-07-29 20:51       ` Linus Torvalds

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=20200731081925.GA5533@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).