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

Highlights from Git 2.28

github.blog

Post reply on HN
Print view View original

101–110 of 147 posts

Re: Highlights from Git 2.28

#101

Post by nitemice »

mklein994 wrote: post #91
neves wrote: post #61

I'm a somewhat advanced user of Git. My coworkers use me as a reference when they have a problem of a difficult merge to solve. I don't follow each Git release, but I also didn't notice a great productivity enhancement for a long time. Sure it is a sign of a mature project, but I'd like to know: What's the somewhat recent Git feature that you really improved your productivity?

git range-diff Very useful to get an overview of what changed after a rebase. https://git-scm.com/docs/git-range-diff

Thank you for mentioning this. I wrote my own bash script to do something similar ages ago, but I'm betting this will be much less janky.

Re: Highlights from Git 2.28

#102

Post by nitemice »

imron wrote: post #100
merb wrote: post #80

Earlier quoted context omitted.

git switch/git switch -c so much better than git checkout and the confusing switches.

Not for me. Those confusing switches are already ingrained in my memory (or hidden away behind aliases) and now I find it more confusing that git is recommending new and different commands to do things that I've been doing a fixed way for years. `git restore ` instead of `git checkout -- `is another one.

Well, I guess the good thing here is that they're not going to remove the old checkout behaviour. And these new commands are much easier to use and understand for a beginner.

Re: Highlights from Git 2.28

#103

Post by fiddlerwoaroof »

jayd16 wrote: post #98
setpatchaddress wrote: post #87

Earlier quoted context omitted.

git worktree. Godsend if you regularly need to work on multiple branches simultaneously.

What does worktree provide that a fresh local clone doesn't?

Reduced disk space usage for large repositories. And a convenient way to manage all your clones

Re: Highlights from Git 2.28

#104

Post by war1025 »

DangitBobby wrote: post #97
chrisshroba wrote: post #73

Earlier quoted context omitted.

Just curious - what reasons do people have for not using master?

Though in the context of git, master is not intended to be a reference to master/slave [1], it is ostensibly widely mis-identified as such. The change therefore is being made by many as an attempt to be more inclusive. I pulled this [2] Bitbucket blog entry from the original article if you want to read what they have to say. 1. https://twitter.com/xpasky/status/1271477451756056577?s=20 2. https://bitbucket.org/blog/m…

I feel like on the one hand my opinion is "this is stupid and doesn't matter", which makes me think the change was not needed.

But also my opinion is "this is stupid and doesn't matter", which makes me not really care that they did I guess.

Re: Highlights from Git 2.28

#105

Post by monocularvision »

setpatchaddress wrote: post #87
neves wrote: post #61

I'm a somewhat advanced user of Git. My coworkers use me as a reference when they have a problem of a difficult merge to solve. I don't follow each Git release, but I also didn't notice a great productivity enhancement for a long time. Sure it is a sign of a mature project, but I'd like to know: What's the somewhat recent Git feature that you really improved your productivity?

git worktree. Godsend if you regularly need to work on multiple branches simultaneously.

“Let me share the Good News of git worktrees” is a thing I say often in our work Slack.

Re: Highlights from Git 2.28

#106

Post by lzutao »

mklein994 wrote: post #91
neves wrote: post #61

I'm a somewhat advanced user of Git. My coworkers use me as a reference when they have a problem of a difficult merge to solve. I don't follow each Git release, but I also didn't notice a great productivity enhancement for a long time. Sure it is a sign of a mature project, but I'd like to know: What's the somewhat recent Git feature that you really improved your productivity?

git range-diff Very useful to get an overview of what changed after a rebase. https://git-scm.com/docs/git-range-diff

Really nice. I hope GitHub use this option soon.

Or maybe not: I guess it's kinda slow and heavy on computation.

Re: Highlights from Git 2.28

#107

Post by MarkSweep »

jayd16 wrote: post #98
setpatchaddress wrote: post #87

Earlier quoted context omitted.

git worktree. Godsend if you regularly need to work on multiple branches simultaneously.

What does worktree provide that a fresh local clone doesn't?

If it's a multi-gigabyte repo that you are cloning over a slow VPN, it speeds things up quite a bit.

Re: Highlights from Git 2.28

#108

Post by umvi »

DangitBobby wrote: post #97
chrisshroba wrote: post #73

Earlier quoted context omitted.

Just curious - what reasons do people have for not using master?

Though in the context of git, master is not intended to be a reference to master/slave [1], it is ostensibly widely mis-identified as such. The change therefore is being made by many as an attempt to be more inclusive. I pulled this [2] Bitbucket blog entry from the original article if you want to read what they have to say. 1. https://twitter.com/xpasky/status/1271477451756056577?s=20 2. https://bitbucket.org/blog/m…

"ignorance is causing people to take offense when none was intended and instead of trying to educate people we can instead just make a greater effort to not offend them"

Re: Highlights from Git 2.28

#109

Post by umvi »

sildur wrote: post #72
romanoderoma wrote: post #69

Earlier quoted context omitted.

IMHO the only problem is what people wanna see in words. master/slave has been with us since forever ( https://news.ycombinator.com/item?id=23969906 ) and describes a relationship between two entities where one is the controller and the other is controlled, in many religions (including the most popular one) there is still a master God (or more than one) and believers are slave to God (with the capital G) But in Git t…

Americans have issues. A lot of issues to be honest. Add to the mix their fervor about what they think is right with their utter disregard about what the rest of the world has to say about it, and you will get an interesting recipe for neocolonialism.

Not all Americans, just a very passionate, vocal subset of Americans

Re: Highlights from Git 2.28

#110

Post by SomaticPirate »

neves wrote: post #61

I'm a somewhat advanced user of Git. My coworkers use me as a reference when they have a problem of a difficult merge to solve. I don't follow each Git release, but I also didn't notice a great productivity enhancement for a long time. Sure it is a sign of a mature project, but I'd like to know: What's the somewhat recent Git feature that you really improved your productivity?

Setting up watchman as a Git hook for fsmonitor.

It speeds up git status on large codebases

https://github.com/git/git/blob/master/templates/hooks--fsmo...

Post reply on HN