git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: "Patricia B. C." <pati.camsky@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Can git change?
Date: Fri, 22 Jan 2021 14:31:57 +0100	[thread overview]
Message-ID: <CAP8UFD0fZBdZ6qwDP9_yW7VAfskTKPC7HVSpK4rD=bORuECpJA@mail.gmail.com> (raw)
In-Reply-To: <CAK8LAYVZKjbMEDWTyvQv2eY+qR0qw1=mn=c4KCZvit7gsqTibA@mail.gmail.com>

Hi,

On Fri, Jan 22, 2021 at 2:05 PM Patricia B. C. <pati.camsky@gmail.com> wrote:
>
> Hello!
> My name is Patricia and I work as a software engineer in Brazil. I
> also teach sometimes at Le Wagon, a programming school.
> I brought the discussion about changing our repositories' branch to
> main instead of master. The response of one of the owners was that
> "Git has not changed it, so we will not change". So here I was,
> wondering if maybe Git would hear me out :)
> Do you have any thoughts on it?

There have been a lot of discussions about this topic. You can find
some pointers to them (though maybe not the most recent ones) in the
article "The history of `master` in Git" in:

https://git.github.io/rev_news/2020/07/29/edition-65/

There has been also an official statement by the Conservancy and the
Git PLC (Project Leadership Committee):

https://sfconservancy.org/news/2020/jun/23/gitbranchname/

Best,
Christian.

  reply	other threads:[~2021-01-22 13:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 12:59 Can git change? Patricia B. C.
2021-01-22 13:31 ` Christian Couder [this message]
2021-01-22 18:46   ` Junio C Hamano
2021-01-22 22:43     ` Martin von Zweigbergk
2021-01-23  2:27       ` Junio C Hamano
2021-01-23 12:56         ` RES: " Patricia B. C.
2021-01-25 16:28           ` Johannes Schindelin
2021-01-26  1:58             ` Junio C Hamano
2021-01-26 12:32               ` Patricia B. C.
2021-03-09 14:54               ` Daniel Gruesso
     [not found]             ` <CAFdpPnBG==5L6hwH6h2JTFtYVQqLZUcCi4+wzL_cpKKg_X3yoA@mail.gmail.com>
2021-03-10 21:03               ` Johannes Schindelin
2021-03-10 21:39                 ` Junio C Hamano

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='CAP8UFD0fZBdZ6qwDP9_yW7VAfskTKPC7HVSpK4rD=bORuECpJA@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pati.camsky@gmail.com \
    /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 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 NNTP newsgroup(s).