All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santiago Torres Arias <santiago@nyu.edu>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
	James Ramsay <jramsay.com.au@syl.local>,
	Bryan Turner <bturner@atlassian.com>
Subject: Re: Consensus on a new default branch name
Date: Mon, 15 Jun 2020 17:10:55 -0400	[thread overview]
Message-ID: <20200615211055.7fggbfnjk2mawb6h@LykOS.localdomain> (raw)
In-Reply-To: <20200615205722.GG71506@syl.local>

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

On Mon, Jun 15, 2020 at 02:57:22PM -0600, Taylor Blau wrote:
> 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.

I've been refraining myself from commenting (specially with so many
passionate voices on [1]), but I'm happy that this is happening. While I
personally don't see anything offensive in 'master', I think it's
worthwhile to try to accomodate more people in the community. As always,
it's harder to identify what is bothering a particular group if you are
not part of that group. Kudos to the community (and to you Taylor) for
trying to move this topic forward in a constructive fashion.
 

> 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.

I'm not familiar with how formal consensus is built in this community,
but take this as an explicit +1 from me.

Cheers!
-Santiago

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

  reply	other threads:[~2020-06-15 21:42 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200615211055.7fggbfnjk2mawb6h@LykOS.localdomain \
    --to=santiago@nyu.edu \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=jramsay.com.au@syl.local \
    --cc=me@ttaylorr.com \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.