Fix claim about Git's default branch name #1724
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The blog post about changing the primary branch name of
rust-lang/rust
, as written, claims that the default branch name of Git, the open-source version control tool originally written by Linus Torvalds, has changed. As best I can determine, that's not true, at least as of Git v2.51. The mailing list thread from 2020, linked in the post, certainly does not support this claim. That thread discusses making the default branch name for newly-created repositories configurable, and it causes a warning to be shown if this is not configured (indicating that the default may change in the future), but the default when not configured has not been changed.Conversely, GitHub, the service now owned by Microsoft, did change the default branch name for newly-created repositories on 2020-10-01. Probably this is what we mean instead. Let's change the post to point to that.
cc @shepmaster @Kobzol @carols10cents
Rendered