Live data from Hacker News

Deprecate Use of Master and Slave

bugs.ruby-lang.org

1–10 of 13 posts

Re: Deprecate Use of Master and Slave

#4
post #3

I think Matz' approach is reasonable here, as opposed to most I've read about.

His response is the most reasonable one that I have seen through all of these, non-issue issues that have come up over this idea that master branch is actually referring to slavery. Id really wonder who even thought that master in the context of git was ever a reference to slavery. I have to think they were some high school/college student that some how made the connection while watching history channel late at night after enjoying a Friday evening or something.

Re: Deprecate Use of Master and Slave

#5
post #3

I think Matz' approach is reasonable here, as opposed to most I've read about.

His response is the most reasonable one that I have seen through all of these, non-issue issues that have come up over this idea that master branch is actually referring to slavery. Id really wonder who even thought that master in the context of git was ever a reference to slavery. I have to think they were some high school/college student that some how made the connection while watching history channel late at night…

I think it's pretty obvious that master gets its taint from the common master-slave usage.

That usage should be changed to leader/follower most likely.

I haven't renamed my default branches, myself, because "master" alone does not imply master/slave.

Re: Deprecate Use of Master and Slave

#7

I would suggest 'liege' and 'vassal' although the 'm-word' and the 's-word' might be an alternative.

I actually kind of like 'liege' and 'vassal': if we really need to replace the current terminology, I'd definitely be open to 'liege'/'vassal'.

I'm going to assume you were joking about 'm-word' and 's-word', because there is no world in which I can imagine people having technical discussions while saying that...

Post reply on HN