Re: Rename offensive terminology (master)
- From
- James Ramsay <james@jramsay.com.au>
- Date
- Jun 15, 2020, 00:34 UTC
- Message-ID
- <42EBA147-1034-4CA2-8A85-AAF023FE3781@jramsay.com.au>
- In-Reply-To
- <nycvar.QRO.7.76.6.2006091126540.482@ZVAVAG-DN14RQO.ybpnyqbznva>
Show 7 quoted lines
> As mentioned elsewhere in this thread, Don (Cc:ed) and I started > working > on this, and I just submitted it: > https://lore.kernel.org/git/pull.656.git.1591823971.gitgitgadget@gmail.com/ > That patch series adds a config variable allowing to override the > default > name of the default branch.
Thanks Johannes and Don for your work on the patch! And Billy for sharing your investigations and thoughts on naming.
> Billy then shared this information with James Ramsay of GitLab to > discuss how GitHub and GitLab can coordinate on changing the default > branch name in new repositories. Here is the GitLab ticket to track > their progress: https://gitlab.com/gitlab-org/gitlab/-/issues/220906
Yes, we are investigating the changes needed to support changing the default branch name of new projects created in GitLab.
Show 5 quoted lines
> Tentatively, I would like to propose having this meeting in the coming > week, via Zoom, just like we did the Virtual Contributor Summit last > September. > > Could I ask all interested parties to reply to this email?
Great idea - thanks Emily! Please include me in the invitation.