Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

it should be noted that git (the binary) is also in the process of deprecating `master`.

This is the message I get on my machine when running git init:

  hint: Using 'master' as the name for the initial branch. This default branch name
  hint: is subject to change. To configure the initial branch name to use in all
  hint: of your new repositories, which will suppress this warning, call:
  hint: 
  hint:  git config --global init.defaultBranch <name>
  hint: 
  hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
  hint: 'development'. The just-created branch can be renamed via this command:
  hint: 
  hint:  git branch -m <name>
  Initialized empty Git repository in /tmp/test


I wouldn't say it's in the process of deprecating "master". It's just reminding user that they shouldn't plainly assume that the default initial branch is, or will always be, named "master".


https://lore.kernel.org/git/xmqqwnu8z03c.fsf@gitster.g/

Based on this it does appear to be deprecated, the current favourite is 'main'

There are references in code to `PREPARE_FOR_MAIN_BRANCH`.

You can see some commentary on the mailling lists: https://lore.kernel.org/git/CAMP44s3DExJ-F=MKhKyupr5M0RDvr8k...


TIL! OK, seems you're right: master seems to be about to be deprecated as the default initial branch.


Why do you think this means that git is deprecating master?

Similarly, GitHub claims that git is making similar changes, and links to a "Statement" that actually says the opposite, and a code change that also does not include anything like making that change (both are from June 2020). Since GitHub's claim is obviously in error, I wonder if it's malice or incompetence.

Is there some other evidence that git is going to deprecate master?


Based on my comment here: https://news.ycombinator.com/item?id=26488240

The 'hint' is nicely worded, but there is sufficient evidence of a pending name change (likely to `main`) for the default.


Huh. You're right. Horrifying.


I just tested this and don't get any message.

What version are you using?


> init: provide useful advice about init.defaultBranch

> To give ample warning for users wishing to override Git's the fall-back for an unconfigured `init.defaultBranch` (in case we decide to change it in a future Git version), let's introduce some advice that is shown upon `git init` when that value is not set.

https://github.com/git/git/commit/675704c74dd4476f455bfa91e7...

    git tag --contains 675704c74dd4476f455bfa91e72eb9e163317c10 | grep -v rc
    v2.30.0
    v2.30.1
    v2.30.2
    v2.31.0


I get this on version 2.30.1 so presumably a 2.30 change. I don't think they're planning to move to main for definite, just that they're preparing people to stop treating `master` as always the default branch


git version 2.30.2




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: