Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New features from the last few versions of Git

blog.github.com

Post reply on HN
Print view View original

41–50 of 50 posts

Re: New features from the last few versions of Git

#41

Post by ComplicatedGitn »

ShabbosGoy wrote: post #33
systems wrote: post #24

Earlier quoted context omitted.

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

I would have an aneurysm if one of my coworkers or teammates didn’t know how to use git. The documentation is widely available, there are exactly zero excuses available.

Like a product manager? You think it's reasonable to understand all the nuances and capabilities of an obtuse CLI tool that manages concurrent history? What you probably mean is the simplified concepts of Git without the capabilities to alter the interaction effects. You come off as the typical condescending developer who secretly looks down on people with different interests and responsibilities because they don't understand YOUR JOB.

Re: New features from the last few versions of Git

#42

Post by peff »

daveFNbuck wrote: post #30
peff wrote: post #20

Earlier quoted context omitted.

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.

Er, sorry, I meant to say "...the new features in Git v2.17".

I think that keeps it clear but without making it overtly look like a release announcement.

Re: New features from the last few versions of Git

#43

Post by pjungwir »

The --color-moved feature sounds really nice!

Something I've seen in Github but not in Git is how in a red/green line, the individual changed characters are a brighter red/green than the rest. Is it possible to get that in CLUI git?

Here is a workflow I use often that I'm amazed isn't supported on Github: First I run `git log path/to/file` to see the commits for just that file. Then in a separate window I start copy/pasting SHAs to see the whole file at each commit: `git show abc123:path/to/file` ... `git show def456:path/tofile` ... etc. It's a little tedious, but it can really help to see what's going on.

It would be so much easier to do this in a browser with links and a back/forward button! In Github I can see the history of a single file, e.g. at https://github.com/pjungwir/topiary/commits/master/lib/topia... But from there I can't see that file at each commit. (Instead there are two links that both show me the commit's full diff, and another link back to the root of the repo.) I wish there were an easy way I could just browse forward and back, keeping the current file! Am I missing something?

Re: New features from the last few versions of Git

#44

Post by hannnoi »

ComplicatedGitn wrote: post #41
ShabbosGoy wrote: post #33

Earlier quoted context omitted.

I would have an aneurysm if one of my coworkers or teammates didn’t know how to use git. The documentation is widely available, there are exactly zero excuses available.

Like a product manager? You think it's reasonable to understand all the nuances and capabilities of an obtuse CLI tool that manages concurrent history? What you probably mean is the simplified concepts of Git without the capabilities to alter the interaction effects. You come off as the typical condescending developer who secretly looks down on people with different interests and responsibilities because they don't u…

The original comment was referring to coders. It's not a lot to ask people who are working on code to know how to use basic git commands.

Re: New features from the last few versions of Git

#45

Post by blueline »

bobbyi_settv wrote: post #37
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…

I was going to say that just from the title, they're not really representing themselves as being git, but then in the body of the post, they actually use "us" to refer to git > Git v2.16 adds a new fsmonitor hook that relies on the operating system to tell us what has changed. Doing so allows us to avoid the repeated stat()

arent't they using "us" to refer to "us, the programmer using git" as in "...to tell us, the user of git, what has changed"?

Re: New features from the last few versions of Git

#46

Post by daveFNbuck »

peff wrote: post #42
daveFNbuck wrote: post #30

Earlier quoted context omitted.

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.

Er, sorry, I meant to say "...the new features in Git v2.17". I think that keeps it clear but without making it overtly look like a release announcement.

Ok, I think that does actually make things a bit more clear. Thanks for writing these up, by the way!

Re: New features from the last few versions of Git

#47

Post by abhishekjha »

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…

I had raised this issue of demarcation a few days back [0].

As a newcomer to git a few years back I wasn't able to tell if github is a part of git or not OR can you work with git without a github account. It was confusing to me as github allows some of the exact functionalities offered by git.

[0] https://news.ycombinator.com/item?id=16600666

Re: New features from the last few versions of Git

#48

Post by ShabbosGoy »

ComplicatedGitn wrote: post #41
ShabbosGoy wrote: post #33

Earlier quoted context omitted.

I would have an aneurysm if one of my coworkers or teammates didn’t know how to use git. The documentation is widely available, there are exactly zero excuses available.

Like a product manager? You think it's reasonable to understand all the nuances and capabilities of an obtuse CLI tool that manages concurrent history? What you probably mean is the simplified concepts of Git without the capabilities to alter the interaction effects. You come off as the typical condescending developer who secretly looks down on people with different interests and responsibilities because they don't u…

Dude that’s a total overreaction. I was referring to software engineers. Why would a product manager need to know how to use rebase or bisect?

Re: New features from the last few versions of Git

#49

Post by jcl »

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…

FWIW, I'd expect any git hosting provider -- including gitlab.com and bitbucket.com -- to be similarly eager to evangelize new git releases, since an improvement to git is an improvement to the usability of their offerings. At the very least, encouraging users to upgrade to easier-to-use git versions could reduce support costs and customer churn.

Re: New features from the last few versions of Git

#50

Post by peff »

pjungwir wrote: post #43

The --color-moved feature sounds really nice! Something I've seen in Github but not in Git is how in a red/green line, the individual changed characters are a brighter red/green than the rest. Is it possible to get that in CLUI git? Here is a workflow I use often that I'm amazed isn't supported on Github: First I run `git log path/to/file` to see the commits for just that file. Then in a separate window I start copy/…

Try the diff-highlight script which can be found at:

https://github.com/git/git/tree/master/contrib/diff-highligh...

Post reply on HN