Post AzPRSwuU6RSQKiFcbg by quincy@chaos.social
 (DIR) More posts by quincy@chaos.social
 (DIR) Post #AzPOinVwVKnLxmdZHk by musicmatze@social.linux.pizza
       2025-10-20T18:25:42Z
       
       0 likes, 0 repeats
       
       Did you know that the #rust #rustlang project will soon break everyones workflows?#git #github
       
 (DIR) Post #AzPOu97qUhpAAumGSu by musicmatze@social.linux.pizza
       2025-10-20T18:27:43Z
       
       0 likes, 0 repeats
       
       apparently, their promises only apply to the rustc users, not to their contributors.
       
 (DIR) Post #AzPQDnFJeRYG3xChtI by quincy@chaos.social
       2025-10-20T18:42:26Z
       
       0 likes, 0 repeats
       
       @musicmatze how?
       
 (DIR) Post #AzPRJ17daTxiV7fQaO by musicmatze@social.linux.pizza
       2025-10-20T18:54:35Z
       
       0 likes, 0 repeats
       
       @blyxyas https://blog.rust-lang.org/inside-rust/2025/10/16/renaming-the-default-branch-of-rust-langrust/
       
 (DIR) Post #AzPRJqnDTeWakqVqyW by musicmatze@social.linux.pizza
       2025-10-20T18:54:38Z
       
       0 likes, 0 repeats
       
       @nik https://blog.rust-lang.org/inside-rust/2025/10/16/renaming-the-default-branch-of-rust-langrust/
       
 (DIR) Post #AzPRL2uXuKMCd0Vkfo by musicmatze@social.linux.pizza
       2025-10-20T18:54:41Z
       
       0 likes, 0 repeats
       
       @quincy https://blog.rust-lang.org/inside-rust/2025/10/16/renaming-the-default-branch-of-rust-langrust/
       
 (DIR) Post #AzPRSwuU6RSQKiFcbg by quincy@chaos.social
       2025-10-20T18:56:25Z
       
       0 likes, 0 repeats
       
       @musicmatze oh 😬
       
 (DIR) Post #AzPRaVsaUBbyodyEGO by chrysn@chaos.social
       2025-10-20T18:57:45Z
       
       0 likes, 0 repeats
       
       @musicmatze So what, it's just a branch rename, as has happened in many projects.As long as they take care of any GitHub fallout (autoclosed PRs for lack of target) ... for a user in git, that's well managable.
       
 (DIR) Post #AzPRlXzIzHPEXYNFhI by musicmatze@social.linux.pizza
       2025-10-20T18:59:46Z
       
       0 likes, 0 repeats
       
       @nik lucky you.
       
 (DIR) Post #AzPRpcuQdEpixh2Qim by musicmatze@social.linux.pizza
       2025-10-20T19:00:27Z
       
       0 likes, 0 repeats
       
       @chrysn still breaks workflows
       
 (DIR) Post #AzPS5wbdAR6qgS1hvE by musicmatze@social.linux.pizza
       2025-10-20T19:03:29Z
       
       0 likes, 0 repeats
       
       @nik I did not specify that it breaks everyones workflow who is "using rust".I just said "everyones", leaving out which group I mean by that. 😉 IMO branch renames breaks workflows of users of the repository where the rename happens.
       
 (DIR) Post #AzPUNVAq67ooj1zkDQ by chrysn@chaos.social
       2025-10-20T19:29:03Z
       
       0 likes, 0 repeats
       
       @musicmatze https://xkcd.com/1172/ ;-)More seriously: Given how widespread the new default is by now, at some point there's a break-even between breakage from the change and users whose muscle memory needs constant overwriting forcing `master` instead of `main`, esp. when other ma- branches defeat tab complete. That break-even may just as well be now-ish.
       
 (DIR) Post #AzPVtVjPeyMzfwzeEa by musicmatze@social.linux.pizza
       2025-10-20T19:46:02Z
       
       0 likes, 0 repeats
       
       @chrysn it is not the "new default". `git` did never change to `main` as a default branch, only the dominant code forges (shithub and shitlab) did. The default of the tool itself is still `master` and IIRC there are no plans to change that default.
       
 (DIR) Post #AzPWbozLQMKi8qZewi by chrysn@chaos.social
       2025-10-20T19:54:02Z
       
       0 likes, 0 repeats
       
       @musicmatze `ls --sort time | head -n100 | xargs -n1 sh -c 'cat $0/.git/HEAD' | sort | uniq -c` gives me 45 main and 23 master for projects I touch regularly, and that ratio only gets stronger the less I extend this to ages old projects.Looks pretty default to me, and the technical git default comes with a big yellow warning "hint: Using 'master' as the name for the initial branch. This default branch name is subject to change.".
       
 (DIR) Post #AzPXM9XhKwIxD4jeE4 by liketechnik@chaos.social
       2025-10-20T20:02:24Z
       
       0 likes, 0 repeats
       
       @musicmatze @chrysn afaict the plan is to change that default with the next major version (3.0) of git, cf. https://git.kernel.org/pub/scm/git/git.git/tree/Documentation/BreakingChanges.adoc:> In new repositories, the default branch name will be `main`. We have been  warning that the default name will change since 675704c74dd (init:  provide useful advice about init.defaultBranch, 2020-12-11).'main' is also mentioned in the "First-Time Setup" (https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup) as an alternative default branch name.
       
 (DIR) Post #AzPi95B1M9I3Ov69ui by rkaj@mastodon.nu
       2025-10-20T22:03:17Z
       
       0 likes, 0 repeats
       
       @musicmatze For an extremely small value of "everyone".   Multiple repos I have contributed to have made the change before, and made no inconvenience to me.
       
 (DIR) Post #AzQOacE8mQdDnYMvrs by musicmatze@social.linux.pizza
       2025-10-21T05:58:56Z
       
       0 likes, 0 repeats
       
       @chrysn git does that for 5 years at this point and it will change with git 3.0 (whenever this will happen is not known yet AFAIK): https://github.com/git/git/commit/675704c74dd4476f455bfa91e72eb9e163317c10
       
 (DIR) Post #AzQOfVZYwsnwbjiopE by musicmatze@social.linux.pizza
       2025-10-21T05:59:49Z
       
       0 likes, 0 repeats
       
       @rkaj lucky you