I renamed my master branch
slaveowner. To make it more clear.It is software, my friends. It’s not a tribe of people.
Not gonna lie, the master branch thing has been perceived as problematic but I don’t typically see an issue with it. It’s similar to master bedroom or bath.
Kind of fucked up name origin, butI don’t think anyone’s really making a fuss about it.Whatever the fuck you’re doing though feels like some gross, racist fantasy. It’s really weird, dude. If you think that’s funny you might need to go talk to some real people or touch grass.
Wtf are you talking about? It doesn’t have a fucked up name origin at all. It was named “master” as in “master recording”, like in music production. Proof: https://x.com/xpasky/status/1271477451756056577.
Master/slave concepts were never a thing in git. The whole renaming thing was really fucking stupid. Caused plenty of breakage of scripts and tools for absolutely no good reason whatsoever.
Alright. Doesn’t change my main point. Which is the person’s name for the master branch is fucking weird.
Master bedroom and master bath also have nothing to do with slavery.
Please grow up.
it has always bothered me that checkout is overloaded: it can switch branches or discard pending changes in an unrecoverable way.
so, PSA, you can replicate the safe part of checkout with
git switchand the unsafe withgit restore.Ah, I love coherent software.
Switch and restore came later because checkout was problematic.
Just alias stuff like that, make it coherent.
git push master --force
I never understood why we moved away from “trunk”.
No latest branch
