There’s no “slave” convention in git so I’m not sure how it can be considered an issue (I get that drives being master and slave is a bit icky). But then, what is it a master of?
As others have said, “trunk” would have been a more sensible replacement.
It’s a master the same way that an original recording (the final version before mass reproduction) is called a master; mixing and processing the raw media clips into such a recording is called mastering. It’s a convention that has existed long before computers were a thing.
There’s an actual response to the issue at hand in that link; man didn’t just decide to drop a meme and peace out (though I probably would’ve assumed that was the case if it wasn’t for the edit)
It’s about master copy. You have a master copy, and you have the development copies that are a copy of the master which is where you make your changes.
If i had to guess, the problem is that people don’t know how to use git and develop in the master
EDIT:
“In engineering, master–slave is a relationship between two systems in which one controls the other.” (from wikipedia)
Git branches don’t control each other… The term comes from master copy. The term “master” comes from bitkeeper:
Definition of Master copy:
A “master copy” refers to the original version of something from which all duplicates or reproductions are made. It’s kind of like the source recipe in a cookbook—every other version stems from it.
There’s no “slave” convention in git so I’m not sure how it can be considered an issue (I get that drives being master and slave is a bit icky). But then, what is it a master of?
As others have said, “trunk” would have been a more sensible replacement.
It’s a master the same way that an original recording (the final version before mass reproduction) is called a master; mixing and processing the raw media clips into such a recording is called mastering. It’s a convention that has existed long before computers were a thing.
(the image is a hyperlink)
On my app, tapping the image makes it full screen. I had to figure out how to get to the raw Markdown of the post and go from there.
For those who come after: https://slrpnk.net/comment/16864626
There’s an actual response to the issue at hand in that link; man didn’t just decide to drop a meme and peace out (though I probably would’ve assumed that was the case if it wasn’t for the edit)
It’s about master copy. You have a master copy, and you have the development copies that are a copy of the master which is where you make your changes.
If i had to guess, the problem is that people don’t know how to use git and develop in the master
EDIT:
“In engineering, master–slave is a relationship between two systems in which one controls the other.” (from wikipedia)
Git branches don’t control each other… The term comes from master copy. The term “master” comes from bitkeeper:
Once you have a clone of the master repository, you can do work as if you were in the master repository. (see bk ci, bk edit)
Definition of Master copy: A “master copy” refers to the original version of something from which all duplicates or reproductions are made. It’s kind of like the source recipe in a cookbook—every other version stems from it.