Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Maybe I'm missing something, but I'm very confused about what is going
to be changed that you are concerned about.  What is it precisely that
going to be happening (or which you think is going to be happening)
which is causing you concern?


Is it changing the default branch name when creating a new repository?
(Which affects only people creating new repositories)

Is it renaming the master branch for the git repo?  (which affects
people who are developing or tracking git via the repository, as
opposed to using a pre-packaged git provided by their Linux
Distributions / OS).

Is it improving the tools so that other projects can more easily
rename their primary development branch from master to main?  (Which
many projects have been doing *already*, without not a lot of Sturm
und Drang as near as I can tell, at least in many/most cases.)

Is it removing places in the git program where "master" is treated
specially (e.g., in how the default text for merge descrtipion is
worded)?

What, specifically, is the "backwards incompatible change" that you
are most worried about?  Because many projects have already been
renaming their primary development branch from master to main
*already*.

						- Ted



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux