public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
	Andreas Schwab <schwab@suse.de>, Paul Eggert <eggert@cs.ucla.edu>,
	Florian Weimer <fweimer@redhat.com>, DJ Delorie <dj@redhat.com>,
	"Ryan S. Arnold" <ryan.arnold@gmail.com>,
	Jakub Jelinek <jakub@redhat.com>,
	Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: Re: Rename "master" branch to "main" for glibc 2.35 release.
Date: Mon, 31 Jan 2022 17:49:14 -0500	[thread overview]
Message-ID: <fcdb70de-b1b5-5f44-b90a-498b4ce5943c@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2201311609360.816123@digraph.polyomino.org.uk>

On 1/31/22 11:19, Joseph Myers wrote:
> On Sat, 29 Jan 2022, Carlos O'Donell via Libc-alpha wrote:
> 
>> My proposal is to rename the development and release branches at the point
>> that glibc 2.35 branches:
>>
>> * master -> main
>>
>> * release/2.35/master -> release/2.35/main
>>
>> No alias would be provided for the master branch; we would immediately
>> start using 'main' as the development branch.
> 
> I strongly disapprove of the approach of renaming an existing branch 
> without providing an alias.  Branches aren't just consumed by active 
> developers, there are many people with their own checkouts, automatically 
> updating mirrors, etc., many of which may be useful to their users without 
> much active maintenance and without anyone following glibc mailing lists; 
> it's gratuitous to break them.

Just for clarity then, if we do the work to support "main" and "master", and add an alias
from "master" to "main" (git status would show as being on "main"), would that have
your support?

-- 
Cheers,
Carlos.


  parent reply	other threads:[~2022-01-31 22:49 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 [this message]
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
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=fcdb70de-b1b5-5f44-b90a-498b4ce5943c@redhat.com \
    --to=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=maxim.kuvyrkov@linaro.org \
    --cc=ryan.arnold@gmail.com \
    --cc=schwab@suse.de \
    /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).