Originally posted by tomas
View Post
Announcement
Collapse
No announcement yet.
Git 2.28 Now Shipping With Feature For Configurable Default/Main Branch Name
Collapse
X
-
Originally posted by liberostelios View PostGit is quite a complex system. If people working with it get confused because of the minuscule difference of meaning between "master" and "main", maybe you shouldn't work with them in the first place.
This is software development, after all. Software malfunction is called a "bug" and before "master" we had "trunk"! Let's not pretend we are care much about how we interpret our terminology based on linguistics. We'll adopt and will be fine!
Code:git add ./* git commit -m "Title" -m "Reasoning" git push
You also have apparently never see how many people on here don't even use it because of *reason here that is just not understanding how git even works* is a thing? It won't fuck me up, but it will fuck up plenty of others who don't live and breath git. You're a moron to say otherwise. Other people still even main other source control systems today because it's just what they already like.
Also, thinking about it a little bit more. There is a word we already are familiar with and that could be a great default name for a branch you probably shouldn't fuck with in a default git setup: upstream. Upstream instills the same idea as a master branch, by definition, and is already well defined in the git community. That would have been a much more sane switch for the remote branch name.Last edited by abott; 28 July 2020, 06:21 PM.
Comment
-
Originally posted by abott View PostAlso, thinking about it a little bit more. There is a word we already are familiar with and that could be a great default name for a branch you probably shouldn't fuck with in a default git setup: upstream. Upstream instills the same idea as a master branch, by definition, and is already well defined in the git community. That would have been a much more sane switch for the remote branch name.
When you create a repository in mercurial, your default branch is named 'default' and when you clone a repo, the primary remote is also named 'default'. This led to a lot of instances of 'hg pull default default' and other silliness.
When I clone a git repo, I usually keep the remote for my fork on gitlab/github/whatever as 'origin' and add another remote for the upstream repository and, yup, I name it 'upstream'.
I'd much rather pull/push to 'upstream/main' than 'upstream/upstream', or worse, 'origin/upstream'.
- Likes 1
Comment
-
Originally posted by abott View Post
You do realize most people don't actually know how to use git well, right? If it goes outside the scope of:
Code:git add ./* git commit -m "Title" -m "Reasoning" git push
There is a word we already are familiar with and that could be a great default name for a branch you probably shouldn't fuck with in a default git setup: upstream.
- Likes 1
Comment
-
Originally posted by Veerappan View Post
I think I dislike 'upstream' for the same reason I disliked 'default' in Mercurial.
When you create a repository in mercurial, your default branch is named 'default' and when you clone a repo, the primary remote is also named 'default'. This led to a lot of instances of 'hg pull default default' and other silliness.
When I clone a git repo, I usually keep the remote for my fork on gitlab/github/whatever as 'origin' and add another remote for the upstream repository and, yup, I name it 'upstream'.
I'd much rather pull/push to 'upstream/main' than 'upstream/upstream', or worse, 'origin/upstream'.
I picked the names "master" (and "origin") in the early Git tooling back in 2005. (this probably means you shouldn't give much weight to my name preferences ) I have wished many times I would have named them "main" (and "upstream") instead.
- Likes 1
Comment
-
Originally posted by abott View PostYou do realize most people don't actually know how to use git well, right?
As far as I know, I'm the only one who takes any advantage of the distributed part of a DVCS... working with multiple clones in parallel, and setting them up as remotes for each other, so I can cherry-pick bits from "highly experimental" into "test and merge".
- Likes 1
Comment
-
bug77 No, that is not "what it is supposed to be". The initial branch in git is just that: the initial branch in git. What value and interpretation you attach to it is completely work flow specific and not determined by git. In no way is the initial branch, that just happens to be named "master", in any shape or form a "master copy", unless you use it in a way that would make it so (I don't see how). Can we please stop this nonsense notion that the name "master" was chosen to mean "master copy", when clearly most of the evidence points to the name actually being inspired by Bitkeeper that does not support multiple branches in a repo but instead have the notion of master/slave repositories.
See
https://mail.gnome.org/archives/desk.../msg00066.html
And
https://github.com/bitkeeper-scm/bit....ask#L231-L232
For this demo, we will need to create a small program which we will then push to the master repository. We are then going to modify the file on both the master and slave repository and then merge the work. For the sake of simplicity, we are doing work in the master repositoryLast edited by tomas; 29 July 2020, 11:55 AM.
- Likes 1
Comment
Comment