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

81–90 of 147 posts

Re: Highlights from Git 2.28

#81

Post by damnyou »

divbzero wrote: post #49
jayd16 wrote: post #30

I just came back to git and gitlab from Perforce and while it's felt like coming home and some things are improving around submodules and LFS there's still a lot of rough edges I'd like to see smoothed over. Its not easy to set up git config settings for a distributed team. I assume for security reasons a repo can't configure its own settings just from a pull but even still I want that functionality. Why do I check i…

Along the same vein, I’d love to be able to configure client-side hooks [1] automatically on clone. [1]: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

Use a configuration management system or simply have a custom clone script that users can curl | sh.

Re: Highlights from Git 2.28

#82

Post by sildur »

WorldMaker wrote: post #74
sildur wrote: post #70

Earlier quoted context omitted.

In the rest of the world is not as problematic, as we associate master with teacher. But we are used to America forcing their culture down our throats. Like they did when tried to force down their hatred for the police on us. So, another one to the list. It would be nice if some day they tried to consider how the rest of the world sees things. For a change.

> In the rest of the world is not as problematic, as we associate master with teacher. Every word has more than one association. The argument is not that every association for the word is negative, but that one association is extremely negative, and we have the ability to use words that have fewer negative associations, so why shouldn't we use words with fewer negative associations? That extremely negative associatio…

Ah, yes. The old “if you don’t think like me you are wrong.” We are also used to that condescending attitude. Very American. But, as surprising as may be, there are other cultures in this world. In mine, master is a word associated to teacher. You see the issue as more recent because it is happening right now. The scars are still bleeding. Maybe this is why you all overreact so much to simple words. To overcompensate.

Re: Highlights from Git 2.28

#83

Post by augusto-moura »

jancsika wrote: post #32
augusto-moura wrote: post #15

Earlier quoted context omitted.

If you are using Tmux, you can use thmux-fingers[1] or tmux-thumbs[2], both create Vimium like shortchuts for urls and git hashes that once pressed copy the link to clipboard or the tmux buffer. Then you can just `git show` and `Ctrl-shift-V` or `Ctrl-b ]`. There's a lot of resources that can be yanked with tmux-fingers, kubernetes resources, ips and others [1] https://github.com/Morantron/tmux-fingers [2] https://gi…

But that isn't a standard part of tmux, right?

It's not, but is really easy to setup with tmux-plugins

Re: Highlights from Git 2.28

#84

Post by JoshTriplett »

jancsika wrote: post #9

Someone please give me the missing link here: 1. I do `git log` which helpfully pipes to `more` where I can use vim-stsyle search to find the commit I'm interested in. 2. I find the relevant commit. 3. Now I want to `git show` that commit. Currently I double click on the human unreadable commit, copy it, quit `more` to get back to the command line, type `git show`, then paste the commit. Navigate, click-click, shortc…

First, the simple optimization for Linux systems: double-click on the commit hash, q, git show, middle-click to paste. That's a simpler copy-paste. I do that surprisingly often, when browsing repositories.

But for a repository I do regular development in, vim with the "fugitive" mode works very well. You can just use :Glog, and browse, hitting enter on a commit to show the full commit, or on a tree to show the tree, or on a file within a tree to show the file (at that version).

I also use :Gdiff to give a vimdiff of changes, to stage the changes I want to commit, and then :Gcommit to commit them.

Re: Highlights from Git 2.28

#85

Post by _ZeD_ »

jancsika wrote: post #9

Someone please give me the missing link here: 1. I do `git log` which helpfully pipes to `more` where I can use vim-stsyle search to find the commit I'm interested in. 2. I find the relevant commit. 3. Now I want to `git show` that commit. Currently I double click on the human unreadable commit, copy it, quit `more` to get back to the command line, type `git show`, then paste the commit. Navigate, click-click, shortc…

Have you tried graphical git clients? Try the Eclipse git plugin. For real! It's the most intuitive tool to deal with git histories

Re: Highlights from Git 2.28

#86

Post by paxswill »

codys wrote: post #40
Myrmornis wrote: post #20

Earlier quoted context omitted.

You could use `git log -p` instead of `git log` so that the diff is included. To navigate efficiently between the commits, you could pre-seed less with a regex that matches commit (and file) lines, so that "n" and "N" jump from one commit (or file) to the next, something like this LESS="-R --pattern ^(commit|diff) " git log -p Delta[1] makes this convenient: delta --navigate. [1] https://github.com/dandavison/delta (…

The one issue I've seen with using `-p` here is that `git log -p` has worse performance when compared to plain `git log` because it needs to calculate diffs, and when searching in less ends up searching the diff contents (even when this is not desired)

If you know the specific string (or regex) you’re searching for in the commit messages, combining `-p` with one of the pickaxe [0] options might be a bit faster.

0: http://www.philandstuff.com/2014/02/09/git-pickaxe.html

Re: Highlights from Git 2.28

#87

Post by setpatchaddress »

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.

Re: Highlights from Git 2.28

#89

Post by Naac »

JoshTriplett wrote: post #84
jancsika wrote: post #9

Someone please give me the missing link here: 1. I do `git log` which helpfully pipes to `more` where I can use vim-stsyle search to find the commit I'm interested in. 2. I find the relevant commit. 3. Now I want to `git show` that commit. Currently I double click on the human unreadable commit, copy it, quit `more` to get back to the command line, type `git show`, then paste the commit. Navigate, click-click, shortc…

First, the simple optimization for Linux systems: double-click on the commit hash, q, git show, middle-click to paste. That's a simpler copy-paste. I do that surprisingly often, when browsing repositories. But for a repository I do regular development in, vim with the "fugitive" mode works very well. You can just use :Glog, and browse, hitting enter on a commit to show the full commit, or on a tree to show the tree,…

>> First, the simple optimization for Linux systems: double-click on the commit hash, q, git show, middle-click to paste. That's a simpler copy-paste. I do that surprisingly often, when browsing repositories.

Yes, I also double-click on the commit hash and copy it. But I wish there was an incrementing index starting from the top of git log, such that say the 15th commit down, I could just say `git show 15` and see that diff, instead of having to copy and paste the commit ID ( and use my mouse )

Re: Highlights from Git 2.28

#90

Post by acdha »

mbakke wrote: post #79
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?

As someone doing lots of merges in a big and active project, git rerere has saved me hours whenever I need to redo a complicated merge. It's not at all new according to a quick grep of RelNotes, but I only recently discovered it, so it is new to me.

Conversely, I hit that years ago (long-running migration tarpit) and forgot about it until I setup a clean home directory on a system which didn’t have my dotfiles repo and thought I’d hit a major Git regression. It saves you time on exactly where you need it the most.
Post reply on HN