Re: Rename "master" branch to "main" for glibc 2.35 release.

[Mike Frysinger <vapier@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

On 29 Jan 2022 21:10, DJ Delorie wrote:
> 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.

the docs will change, or they're obsolete.  the world didn't fall down when
we moved from cvs to git.  or any other toolchain project that moved from
cvs to git, or to svn and then git.  this is a lot of drama for nothing.

> > 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.

the docs already exist.
https://sourceware.org/glibc/wiki/GlibcGit/MigrationToMain
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]