Warning for anyone using Git 2.17 on Windows with Jenkins
New features from the last few versions of Git
11–20 of 50 posts
Re: New features from the last few versions of Git
#12Please use the original announcement https://marc.info/?l=git&m=152270220826214&w=2 (or change the title to something else such as "Some interesting new features of git 2.17")
Re: New features from the last few versions of Git
#13The post itself is informative. But the title is deliberately confusing. This is not the release announcement. We should not let GitHub take over the Git brand like they try to do with blog posts like this one.
Most coders these days say they use git while in reality the have no clue how it works and how to use it. They just use the buttons of tools and services built on top of it and hope for the best. We would all win if we could collaborate via the nice functionality Git itself provides.
Re: New features from the last few versions of Git
#14Earlier quoted context omitted.
I don't know... While the title might give that impression, the opening paragraph seems pretty up-front about distinguishing "the open source Git project" from GitHub ("here's our look..."). They don't even mention their not-insignificant contributions to the project, nor do they say things like "we added [x]", even though they legitimately might be able to in some cases. And, given their line of work, it would be ki…
Out of curiosity, would you be surprised by: - Git 2.17 is now available (gitlab.com) - Git 2.17 is now available (bitbucket.com) The point is, by publishing this kind of posts, Github is making you associate git with Github. Anecdote example: my university lecturer calls Github APIs "git APIs". While that might not be a bad thing, it blurs the boundary between an open source project and a company. I can already imag…
I think GitHub has done a great job being a good steward of the git project. They welcomed us (GitLab) to events like git merge. Because they made git popular people are sometimes confused about the difference between git and GitHub. But GitHub has done a great job on not muddling the water themselves.
Re: New features from the last few versions of Git
#15Please use the original announcement https://marc.info/?l=git&m=152270220826214&w=2 (or change the title to something else such as "Some interesting new features of git 2.17")
To be fair, the original announcement you linked is unreadable.
Re: New features from the last few versions of Git
#16Earlier quoted context omitted.
Out of curiosity, would you be surprised by: - Git 2.17 is now available (gitlab.com) - Git 2.17 is now available (bitbucket.com) The point is, by publishing this kind of posts, Github is making you associate git with Github. Anecdote example: my university lecturer calls Github APIs "git APIs". While that might not be a bad thing, it blurs the boundary between an open source project and a company. I can already imag…
I think GitHub has done a great job being a good steward of the git project. They welcomed us (GitLab) to events like git merge. Because they made git popular people are sometimes confused about the difference between git and GitHub. But GitHub has done a great job on not muddling the water themselves.
Okay. I guess if you say so then I was just being paranoid and overreacting.
Re: New features from the last few versions of Git
#17Earlier quoted context omitted.
I think GitHub has done a great job being a good steward of the git project. They welcomed us (GitLab) to events like git merge. Because they made git popular people are sometimes confused about the difference between git and GitHub. But GitHub has done a great job on not muddling the water themselves.
Okay. I guess if you say so then I was just being paranoid and overreacting.
I'm not saying that, just giving our point of view. BTW I still meet a lot of people that think GitHub is open source instead of them hosting open source.
Re: New features from the last few versions of Git
#18Earlier quoted context omitted.
I don't know... While the title might give that impression, the opening paragraph seems pretty up-front about distinguishing "the open source Git project" from GitHub ("here's our look..."). They don't even mention their not-insignificant contributions to the project, nor do they say things like "we added [x]", even though they legitimately might be able to in some cases. And, given their line of work, it would be ki…
Out of curiosity, would you be surprised by: - Git 2.17 is now available (gitlab.com) - Git 2.17 is now available (bitbucket.com) The point is, by publishing this kind of posts, Github is making you associate git with Github. Anecdote example: my university lecturer calls Github APIs "git APIs". While that might not be a bad thing, it blurs the boundary between an open source project and a company. I can already imag…
I've had colleagues believe bitbucket is a replacement for git.
I had to explain there's a quite big difference between the two. I assume he had mixed up github with git and correctly deduced bitbucket is an alternative to github.
Also, I got way too excited over the git news to notice that it was github publishing ...
Re: New features from the last few versions of Git
#19The post itself is informative. But the title is deliberately confusing. This is not the release announcement. We should not let GitHub take over the Git brand like they try to do with blog posts like this one. Most coders these days say they use git while in reality the have no clue how it works and how to use it. They just use the buttons of tools and services built on top of it and hope for the best. We would all…
> Most coders these days say they use git while in reality the have no clue how it works and how to use it
Come on, seriously? Where do you work?
Re: New features from the last few versions of Git
#20I'm wondering whether the intention with these sorts of blog posts (GitHub has done several of these in the past[1,2], where they provide a summary of the release notes) is to try to put in people's minds the link that "git" == "GitHub". To be fair, the author is actually the 2nd largest contributor (by commits) to the git project. Just thought it was a bit strange. [1]: https://blog.github.com/2016-11-29-git-2-11-ha…
Thanks for the feedback in this thread (I'm the author). The main goal _is_ to let people know about the new version, and about new features they can use (there are a ton of other new features and a lot of backend speedups and cleanups that I don't bother to highlight, because they're not really actionable by normal users).
I've tried to make the Git vs GitHub distinction clear in the first paragraph without belaboring it, but I agree with the sentiment here that the title muddies things. For future iterations I'll look into something more like "A look at the new features in v2.17".