New features from the last few versions of Git • Hacker News Board

Re: New features from the last few versions of Git

#21

Post by peff » Fri, Apr 06, 2018, 3:23 PM UTC

paradite wrote: post #8

jcl wrote: post #5

Earlier 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…

Try "Git 2.9 is out!": https://blog.bitbucket.org/2016/06/13/git-2-9/

Re: New features from the last few versions of Git

#22

Post by jolmg » Fri, Apr 06, 2018, 3:37 PM UTC

cyphar wrote: post #3

I'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…

It does happen. When we were hiring a couple years back, some candidates seemed to be confusing the two or thought that git was a product of GitHub.

Re: New features from the last few versions of Git

#23

Post by Z0rb » Fri, Apr 06, 2018, 3:37 PM UTC

eafkuor wrote: post #19

TekMol wrote: post #13

The 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?

I know right?! What kind of response is that?

Re: New features from the last few versions of Git

#24

Post by systems » Fri, Apr 06, 2018, 3:41 PM UTC

Z0rb wrote: post #23

eafkuor wrote: post #19

Earlier quoted context omitted.

> 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?

I know right?! What kind of response is that?

I cant tell if this serious or sarcastic

I did see many who use git via say sourcetree, they do just click button to push and pull .. and they dont know much more

I dont think this is bad though

Re: New features from the last few versions of Git

#25

Post by jwilk » Fri, Apr 06, 2018, 3:45 PM UTC

jwilk wrote: post #2

Please use the original title.

I see it's been updated. Thanks!

Re: New features from the last few versions of Git

#26

Post by Froyoh » Fri, Apr 06, 2018, 3:46 PM UTC

I'll never be able to remember all of these new flags they add in. Too bad all these nifty features are all "opt-in".

Re: New features from the last few versions of Git

#27

Post by tpush » Fri, Apr 06, 2018, 3:46 PM UTC

TekMol wrote: post #13

The 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.

I mean, that is true whether they're using GUIs on top of git or git's actual CLI.

Re: New features from the last few versions of Git

#28

Post by jwilk » Fri, Apr 06, 2018, 3:48 PM UTC

rehemiau wrote: post #15

ernesth wrote: post #12

Please 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.

Slightly more readable copy (from the official archive):

https://public-inbox.org/git/xmqq6059z9kz.fsf@gitster-ct.c.g...

Re: New features from the last few versions of Git

#29

Post by nmjohn » Fri, Apr 06, 2018, 3:51 PM UTC

TekMol wrote: post #13

The 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…

> We should not let GitHub take over the Git brand like they try to do with blog posts like this one.

Is there a similar blog post by the actual git team sharing this information? If so, let's link to that - but as I am not aware of one, I do appreciate github's git release announcements because they are typically a much easier way to learn about new git features than reading the entire release emails [0]

[0]: https://www.mail-archive.com/git@vger.kernel.org/msg145986.h...

Re: New features from the last few versions of Git

#30

Post by daveFNbuck » Fri, Apr 06, 2018, 4:13 PM UTC

peff wrote: post #20

cyphar wrote: post #3

I'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 belabori…

I think the title you used is a lot less confusing than "A look at the new features in v2.17". A title like that doesn't mention Git would make me think that GitHub is releasing v2.17 if its own product. I don't think there's a way you can clear this up within the title.