That would make sense for forks, not branches. Although to be fair, the word branch also doesn't make sense for branches (since those don't exactly merge back into the trunk).

[–] yetAnotherUser@discuss.tchncs.de 1 points 21 hours ago

I think it can apply to the most general workflow with branches as well, where branches are used to develop features and then later merge them.

After all, any new branch is basically a "remaster" until merged back in, which is when the original master becomes the remaster.

Sure, the analogy isn't perfect because in music the original master isn't supposed to change – but the entire purpose of a version control system is to change the "master record", i.e. what's deployed to production.