From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Rename "master" branch to "main"?
Date: Tue, 30 Jun 2020 21:24:39 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2006302121460.12346@digraph.polyomino.org.uk> (raw)
In-Reply-To: <fcfeed67-d732-e7c7-1f69-ba5fbc036ab2@redhat.com>
On Tue, 30 Jun 2020, Carlos O'Donell via Libc-alpha wrote:
> My proposal would be to rename the development and current release branch:
>
> * master -> main
>
> * release/2.32/master -> release/2.32/main
Have you reviewed the git hooks and hook configuration to identify
anything that special-cases master or branch names involving "master"?
For example, configuration of which branches do or do not allow
non-fast-forward pushes / merge commits / ...?
Do you have all the wiki updates that would be required prepared? In
particular, detailed instructions for updating existing clones that have
branches tracking master?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-06-30 21:24 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 18:10 Carlos O'Donell
2020-06-30 18:35 ` Paul Eggert
2020-06-30 20:16 ` Carlos O'Donell
2020-06-30 21:08 ` Paul Eggert
2020-06-30 18:59 ` Florian Weimer
2020-06-30 20:14 ` Carlos O'Donell
2020-07-01 9:38 ` Florian Weimer
2020-07-03 15:26 ` Richard Earnshaw
2020-07-03 15:33 ` Carlos O'Donell
2020-06-30 21:24 ` Joseph Myers [this message]
2020-06-30 21:44 ` Carlos O'Donell
2020-06-30 22:56 ` Joseph Myers
2020-06-30 22:59 ` DJ Delorie
2020-07-01 7:17 ` Andreas Schwab
2020-07-01 15:42 ` Carlos O'Donell
2020-07-01 12:29 ` Adhemerval Zanella
2020-07-01 12:49 ` Carlos O'Donell
2020-07-01 13:41 ` Adhemerval Zanella
2020-07-01 16:15 ` Carlos O'Donell
2020-07-01 17:45 ` DJ Delorie
2020-07-01 18:29 ` Paul Eggert
2020-07-01 18:43 ` DJ Delorie
2020-07-02 15:40 ` Zack Weinberg
2020-07-02 16:00 ` Florian Weimer
2020-07-02 16:36 ` Joseph Myers
2020-07-02 20:46 ` Paul Eggert
2020-07-04 16:43 ` Zack Weinberg
2020-07-02 20:58 ` Michael Kerrisk
2020-07-03 15:20 ` Carlos O'Donell
2020-07-04 16:52 ` Pseudoterminal terminology (was Re: Rename "master" branch to "main"?) Zack Weinberg
2020-07-05 14:54 ` J William Piggott
2020-07-06 9:18 ` Michael Kerrisk (man-pages)
2020-07-06 9:13 ` Michael Kerrisk (man-pages)
2020-07-27 20:32 ` Michael Kerrisk (man-pages)
2020-07-27 20:52 ` enh
2020-07-27 20:55 ` enh
2020-07-27 20:59 ` Florian Weimer
2020-07-27 22:48 ` enh
2020-07-28 15:26 ` Michael Kerrisk (man-pages)
2020-07-28 15:32 ` Florian Weimer
2020-07-28 15:44 ` enh
2020-07-28 19:16 ` Michael Kerrisk (man-pages)
2020-07-28 19:18 ` enh
2020-07-28 18:47 ` enh
2020-07-28 19:27 ` Michael Kerrisk (man-pages)
2020-07-28 19:33 ` enh
2020-07-03 15:22 ` Rename "master" branch to "main"? Richard Earnshaw
2020-07-03 15:37 ` Carlos O'Donell
2020-07-13 15:14 ` Carlos O'Donell
2021-01-14 9:21 ` Mike Frysinger
2021-01-14 11:17 ` Siddhesh Poyarekar
2021-01-14 17:54 ` Joseph Myers
2021-01-14 20:56 ` Carlos O'Donell
2021-01-14 21:42 ` Mike Frysinger
2021-01-20 13:49 ` Carlos O'Donell
2021-01-21 0:23 ` Mike Frysinger
2021-01-21 13:30 ` Carlos O'Donell
2021-01-21 13:57 ` Andreas Schwab
2021-01-21 17:06 ` Mike Frysinger
2021-01-21 19:37 ` Carlos O'Donell
2021-01-21 20:19 ` Andreas Schwab
2021-01-22 2:32 ` Mike Frysinger
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=alpine.DEB.2.21.2006302121460.12346@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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.
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).