From: Carlos O'Donell <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>, DJ Delorie <dj@redhat.com>
Cc: fweimer@redhat.com, jakub@redhat.com, libc-alpha@sourceware.org,
schwab@suse.de, joseph@codesourcery.com,
maxim.kuvyrkov@linaro.org
Subject: Re: Rename "master" branch to "main" for glibc 2.35 release.
Date: Tue, 1 Feb 2022 02:25:06 -0500 [thread overview]
Message-ID: <58e76793-a7ea-d663-de9b-065881e45d96@redhat.com> (raw)
In-Reply-To: <70889c7c-2e8c-a5d2-3a03-4fa9d013dab4@gotplt.org>
On 2/1/22 00:05, Siddhesh Poyarekar wrote:
> Agreed, I think that's a point (or at least similar) that Joseph
> raised too; there's no strong reason to break links right away,
> especially for a project that has kept libio untouched for fear of
> breaking programs built with gcc 2.95.
Currently gcc has trunk ref'ing master so you can use both trunk and master.
We could easily, and I don't object to it, have master be a symbolic-ref
for main. This appears to be the only part of the transition for which DJ
and Joseph have strong opinions.
I'll adjust the proposal, and link to Mike's wiki document too.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2022-02-01 7:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 22:32 Carlos O'Donell
2022-01-29 22:45 ` Phil Blundell
2022-01-29 23:33 ` DJ Delorie
2022-01-30 1:35 ` Mike Frysinger
2022-01-30 2:10 ` DJ Delorie
2022-01-30 3:45 ` Mike Frysinger
2022-01-30 2:35 ` Paul Eggert
2022-01-30 5:41 ` Siddhesh Poyarekar
2022-01-31 12:46 ` Florian Weimer
2022-01-31 13:41 ` Andreas Schwab
2022-01-31 14:55 ` Carlos O'Donell
2022-02-01 0:59 ` Dmitry V. Levin
2022-02-01 3:05 ` Carlos O'Donell
2022-01-31 12:50 ` Tulio Magno Quites Machado Filho
2022-01-31 16:19 ` Joseph Myers
2022-01-31 17:59 ` Dan Raymond
2022-01-31 18:04 ` Dan Raymond
2022-01-31 22:49 ` Carlos O'Donell
2022-01-31 23:04 ` Joseph Myers
2022-02-01 3:02 ` Carlos O'Donell
2022-01-31 18:09 ` Adhemerval Zanella
2022-01-31 18:14 ` H.J. Lu
2022-01-31 18:21 ` Adhemerval Zanella
2022-01-31 18:28 ` DJ Delorie
2022-02-01 3:08 ` Siddhesh Poyarekar
2022-02-01 3:44 ` DJ Delorie
2022-02-01 5:05 ` Siddhesh Poyarekar
2022-02-01 7:25 ` Carlos O'Donell [this message]
2022-01-31 20:15 ` Siddhesh Poyarekar
2022-01-31 21:24 ` Adhemerval Zanella
2022-02-01 2:51 ` Siddhesh Poyarekar
2022-02-01 9:49 ` Florian Weimer
2022-02-01 10:26 ` Siddhesh Poyarekar
2022-02-03 5:57 ` Carlos O'Donell
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=58e76793-a7ea-d663-de9b-065881e45d96@redhat.com \
--to=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.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).