3 ms·
I think that there is no need to change these things. If you make a new version control system, then you can use whichever name you think is best (presumably wh
by zzo38computer 6y ago
I think that there is no need to change these things. If you make a new version control system, then you can use whichever name you think is best (presumably whichever one is most descriptive, but not too long), but we need not change existing ones, nor change projects using them to use different names.
I personally don't use git, but the naming of the default branch has nothing to do with it. I use Fossil, which uses "trunk" as the name for the default branch. I don't know what reason they chose this, but I don't really care much; I just use that because it is the software I use (even if some people hate it, which I suppose is inevitable).
I also think that other terminology such as blacklist/whitelist, master/slave, etc need not be changed, unless the old terms are confusing or incorrect, which in some contexts there is the possibility that they might be. In some cases, such as motherboard vs mainboard, BC/AD vs BCE/CE, both sets of terms are in use so it is helpful to know them.
Political correctness has gone mad (although this is nothing new, really).
- EForEndeavour 6y ago> I use Fossil, which uses "trunk" as the name for the default branch. I don't know what reason they chose this, but I don't really care much The "default branch" of a tree is a trunk, from which branches emerge.