Highlights from Git 2.28

#1

Post by programeris » Mon, Jul 27, 2020, 4:59 PM UTC

Highlights from Git 2.28
github.blog

Re: Highlights from Git 2.28

#2

Post by pojntfx » Mon, Jul 27, 2020, 7:18 PM UTC

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

Re: Highlights from Git 2.28

#3

Post by Twisol » Mon, Jul 27, 2020, 7:19 PM UTC

pojntfx wrote: post #2

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

I saw somebody on Twitter call theirs "canon", which I've really taken a liking to. It fits nicely in regular speech too :D

Re: Highlights from Git 2.28

#4

Post by jamesponddotco » Mon, Jul 27, 2020, 7:21 PM UTC

Twisol wrote: post #3

pojntfx wrote: post #2

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

I saw somebody on Twitter call theirs "canon", which I've really taken a liking to. It fits nicely in regular speech too :D

I use, and prefer "trunk" since I rarely use branches, but "canon" might change my mind.

Re: Highlights from Git 2.28

#5

Post by apetresc » Mon, Jul 27, 2020, 7:27 PM UTC

pojntfx wrote: post #2

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

Github has said the most popular one across all their repos is `main`, and that's what they'll be going with themselves.

(Source: https://github.com/github/renaming)

Re: Highlights from Git 2.28

#6

Post by oweiler » Mon, Jul 27, 2020, 7:29 PM UTC

pojntfx wrote: post #2

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

I've seen `main` being used quite often.

Re: Highlights from Git 2.28

#7

Post by TheChaplain » Mon, Jul 27, 2020, 7:35 PM UTC

pojntfx wrote: post #2

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

I renamed all mine to 'senpai'.

Re: Highlights from Git 2.28

#8

Post by solatic » Mon, Jul 27, 2020, 7:36 PM UTC

Twisol wrote: post #3

pojntfx wrote: post #2

I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)

I saw somebody on Twitter call theirs "canon", which I've really taken a liking to. It fits nicely in regular speech too :D

Canon is excellent, but I fear it wouldn't catch on due to its religious origins / connotations.

Re: Highlights from Git 2.28

#9

Post by jancsika » Mon, Jul 27, 2020, 7:36 PM UTC

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, shortcut, 'q', type a command, paste. That's six pieces of business.

That seems very wrong and time-consuming.

How do I go gracefully from browsing git log to git show without retyping/pasting the human unreadable commit? Preferably with fewer than seven steps.

Re: Highlights from Git 2.28

#10

Post by nyanpasu64 » Mon, Jul 27, 2020, 7:42 PM UTC

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…

I use a text-mode UI like tig or gitui.