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

[Paul Eggert <eggert@cs.ucla.edu>]

On 1/29/22 14:32, Carlos O'Donell wrote:
> All other wiki, web, and source references can be adjusted over time.

By "source references" I assume you mean the occurrences of "master" in 
scripts/backport-support.sh and scripts/build-many-glibcs.py. I assume 
these would be updated in very short order. (Or did I miss some 
occurrences?)

I'm in favor of the change, just as I was the last time you asked. Of 
course it will entail work but the amount of effort should be small.


For what it's worth I renamed tzdb's "master" to "main" in March 2021. 
Although tzdb is much smaller than glibc, it has dozens of downstream 
projects and there were some nontechnical complaints (one commenter 
called the change "profoundly silly"). I recall only one technical 
problem being reported, though, and it was minor 
<https://mm.icann.org/pipermail/tz/2021-March/029944.html>. To help 
prevent that problem from occurring with glibc it might be helpful to 
suggest that each developer with a local clone adjust to the change 
after it's installed, by issuing something like the following shell 
commands.

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
git remote prune origin