git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Nov 20, 2020, 19:14 UTC
Message-ID
<20201120191426.jzaiq42mmlocmd6y@chatter.i7.local>
In-Reply-To
<xmqq4kllxcmw.fsf@gitster.c.googlers.com>
On Thu, Nov 19, 2020 at 01:25:27PM -0800, Junio C Hamano wrote:
> The question most useful to ask at this point are to what name
> (fixed? computed?) and what the transition plan would look like.

Right, hence my statement that there are no "concrete plans." I've previously suggested that, should this change be implemented, it makes sense to couple it with another upcoming major compatibility break -- the sha1 deprecation. Perhaps we can start with the following:

Currently:

$ git init Initialized empty Git repository in /var/home/user/foo/.git/ $

New:
$ git init
Initialized empty Git repository in /var/home/user/foo/.git/
 Initial branch: master
  Object format: sha1

Use --initial-branch and --object-format flags to specify other values. $

Show 13 quoted lines
> > It is misleading in the context of git, because it implies that a 
> > branch carrying that name is in some way special compared to other 
> > branches (e.g. like "trunk" in the SVN world). In reality, the 
> > "master" branch is just a branch like all others (and can be missing 
> > entirely or have junk in it), so it really shouldn't be called 
> > "master".
> 
> I find the above answer even more confusing, in the context of major
> projects and hosting sites all moving to 'main'.  If 'master' is
> misleading for all the reasons stated in the above paragraph, 'main'
> would equally be misleading.  In other words, "It is just a branch
> like all others, so it really shouldn't be 'master'" leads to "it
> shouldn't be 'main' or 'primary', either".

In my mind, there are important semantic differences between "main" and "master" that make "main" more acceptable. A town with a single road can reasonably call it the "main road." Similarly, a "mainstream" movement does not imply the existence of any other movements. Etc.

-K
Previous: Felipe ContrerasNext: Brandon Casey
Message 17 of 25 in “The master branch rename, and avoiding another v1.6.0 git-foo fiasco”
  1. Felipe ContrerasNov 13, 2020
  2. brian m. carlsonNov 13, 2020
  3. Felipe ContrerasNov 13, 2020
  4. Theodore Y. Ts'oNov 13, 2020
  5. Felipe ContrerasNov 13, 2020
  6. Theodore Y. Ts'oNov 13, 2020
  7. Felipe ContrerasNov 13, 2020
  8. Michal SuchánekNov 13, 2020
  9. Lukasz NiemierNov 14, 2020
  10. Theodore Y. Ts'oNov 15, 2020
  11. Felipe ContrerasNov 15, 2020
  12. Brandon CaseyNov 19, 2020
  13. Peter HadlawNov 19, 2020
  14. Konstantin RyabitsevNov 19, 2020
  15. Junio C HamanoNov 19, 2020
  16. Felipe ContrerasNov 19, 2020
  17. Konstantin RyabitsevNov 20, 2020
  18. Brandon CaseyNov 19, 2020
  19. Felipe ContrerasNov 20, 2020
  20. Don Goodman-WilsonNov 13, 2020
  21. Ismael LucenoNov 20, 2020
  22. Felipe ContrerasNov 13, 2020
  23. Philippe BlainNov 13, 2020
  24. Felipe ContrerasNov 13, 2020
  25. WhinisNov 23, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.