public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: carlos@redhat.com, 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: Sat, 29 Jan 2022 21:10:40 -0500	[thread overview]
Message-ID: <xnv8y2x9b3.fsf@greed.delorie.com> (raw)
In-Reply-To: <YfXrbDaSXMvWiJHy@vapier> (message from Mike Frysinger on Sat, 29 Jan 2022 20:35:40 -0500)

Mike Frysinger <vapier@gentoo.org> writes:
> what documentation exactly are you concerned about here ?

I don't know, which is a bit frightening.  How many web pages on the
internet talk about glibc's "master" branch?  I pretty regularly run
across web pages that are worse than useless because they rely on "the
old way" and I'd like to avoid that if possible, and leaving behind an
alias is both possible and pretty trivial.

> this is making much ado about nothing.  "fixing" a checkout is a single
> command to change what branch is being used to merge.  even then, it's not
> like the world will explode if someone has to manually fixup their checkout
> once.

Did you write up those instructions?  *I* don't know how to do it, other
than "delete tree; checkout fresh".  Do you know where users will go
searching for those instructions?  Unless you put a highly obvious note
on the top of glibc's wiki home page, I bet most people won't be able to
easily find it.

The internet is a mess and the best instructions are "you don't need to
do anything, it will just work" because of that.

> there's no need to keep "master" redirecting to "main" forever,

There's no reason to not keep it either.


  reply	other threads:[~2022-01-30  2:10 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 [this message]
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
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=xnv8y2x9b3.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=carlos@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=vapier@gentoo.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).