Live data from Hacker News

Gitlab default branch name changes to main

about.gitlab.com

21–30 of 294 posts

Re: Gitlab default branch name changes to main

#21
post #10
post #7

Earlier quoted context omitted.

Master has multiple definitions, yours is not the same as the one git used.

If we're referring to 'master' in the context of master/slave, then that's also not the same as the one git uses

According to the article it does.

Re: Gitlab default branch name changes to main

#22

Another victim of this hysteria. Will surely make a point to switch it back every time I create a repo.

See, that would be making yourself a victim of "hysteria". If you just raised an eyebrow and moved on then your claim that it's "hysteria" might have more weight but you'd have less opportunity to grandstand about it. This is also an amusing choice of terminology because of the origin of the word hysteria but I'm going to guess you didn't do that on purpose.

Re: Gitlab default branch name changes to main

#24

Another victim of this hysteria. Will surely make a point to switch it back every time I create a repo.

I fell too that this master-slave thing is a overstretch and a little hysteria. That being said, I do think 'main' is a better name for what this branch is supposed to be and it might be better for beginners to understand. Of course, 'master' is the term we are all used to and that will cause a lot of confusion and broken pipelines too.

Re: Gitlab default branch name changes to main

#26
post #18

I wonder if a master's degree is also offensive.

Good question - the appears to be "no", since it has a clear origin and meaning unrelated to master/slave relationships.

Agreed. Git has a very painful history of keeping master code where slave code in branches did all the work.

Re: Gitlab default branch name changes to main

#27

I for one think it's great that people are willing to make things a little more accessible for more people. If people want to be part of our community of developers I think it's great that these organizations listen to people who might have a problem with certain terminology. Even though I don't have a problem with those terms, I think it's still worth evaluating if they're worth keeping if it makes it harder for som…

>I for one think it's great that people are willing to make things a little more accessible for more people.

How does this make anything more accessible for anyone?

Re: Gitlab default branch name changes to main

#28
Either

(1) Default name doesn't have inherent value; therefore, changing the default isn't a big deal (low downside), even if the upside is low

(2) "master" is for some reason a better name than "main"

I never see the people complaining about this stuff spelling out a reason why it's a bad idea to change (2), and am forced to conclude that we are in scenario (1).

It seems to me that opinion is much more divided on the amount of upside in changing the name. But if the downside is virtually non-existent, who cares? If this is important to some people, shouldn't we just listen to them, and move on?

Re: Gitlab default branch name changes to main

#30

Another victim of this hysteria. Will surely make a point to switch it back every time I create a repo.

See, that would be making yourself a victim of "hysteria". If you just raised an eyebrow and moved on then your claim that it's "hysteria" might have more weight but you'd have less opportunity to grandstand about it. This is also an amusing choice of terminology because of the origin of the word hysteria but I'm going to guess you didn't do that on purpose.

Do we really have to examine the origin of every word we use rather than according its modern common usage and use in context?
Post reply on HN