Live data from Hacker News

Introducing Git protocol version 2

opensource.googleblog.com

11–20 of 167 posts

Re: Introducing Git protocol version 2

#11
post #8

This is disgusting. So little forsight in the past... At least the outcome of quite useful.

IIRC, they were in a serious time crunch when they drafted/made git. I can't remember the whole story...

I thought Linus Torvalds was almost wholly responsible for the initial development of git? Even so, everything, especially software, is easier in hindsight....

Re: Introducing Git protocol version 2

#13
post #8

This is disgusting. So little forsight in the past... At least the outcome of quite useful.

IIRC, they were in a serious time crunch when they drafted/made git. I can't remember the whole story...

At the time Linus was the sole author/contributor of git, and he needed a replacement for BitKeeper in a hurry. BitKeeper had been made unavailable for Linux kernel development because the proprietor of BitKeeper was really unhappy that Tridge had reverse engineered the protocol and created an open-source client[1] which could talk to the Bitkeeper server. Linus created the first version of git sufficient to do a kernel commit in ten days[2].

[1] https://sourceforge.net/projects/sourcepuller/

[2] https://www.linuxfoundation.org/blog/10-years-of-git-an-inte...

(As Tridge tells the story[3], he telnet'ed to the bk port and typed "help" so it wasn't that much of a reverse engineering effort. :-)

[3] https://lwn.net/Articles/132938/

Re: Introducing Git protocol version 2

#14

Interesting that they took to the Google blog to announce this; is there a corresponding LKML post?

Why LKML? Despite Git's origins from and use by the Linux project, it isn't especially tied to it now.

LKML would presumably be the place for Linux to announce when they adopt this.

The Google open source blog is among the several credible options for this post, since Google employs much of the core Git team, and this post discusses their experience deploying Git protocol v2 at Google.

As noted in the blog text, it's not in a released version of Git yet, just Git master branch. So maybe it'll appear on a dedicated Git announcement list, if any, once that happens.

Re: Introducing Git protocol version 2

#16

Interesting that they took to the Google blog to announce this; is there a corresponding LKML post?

> support for v2 was recently merged to Git's master branch and is expected to be part of Git 2.18

Not yet, but presumably there will be a post like this: https://lkml.org/lkml/2018/4/2/425 when it is released. It is strange that the Google Blog is the first place to announce it through.

Re: Introducing Git protocol version 2

#17
post #8

This is disgusting. So little forsight in the past... At least the outcome of quite useful.

IIRC, they were in a serious time crunch when they drafted/made git. I can't remember the whole story...

s/they/he/. It was Linus himself who alone created git, within a few weeks (two or three). At first it was just a handful of shell scripts, but it was self-hosting pretty early on.

Re: Introducing Git protocol version 2

#18
post #8

This is disgusting. So little forsight in the past... At least the outcome of quite useful.

IIRC, they were in a serious time crunch when they drafted/made git. I can't remember the whole story...

Using BitKeeper as the SCM for the Linux kernel always seemed like a bad idea and when issues between the company and the community peaked git was created.

https://git-scm.com/book/en/v2/Getting-Started-A-Short-Histo...

Re: Introducing Git protocol version 2

#19

The current (and pretty much only, ever, despite Linus having been the creator) maintainer of git is a google employee [1], in case anyone else was wondering. [1] https://en.m.wikipedia.org/wiki/Junio_Hamano

Non-Mobile link for those on desktop: https://en.wikipedia.org/wiki/Junio_Hamano

Re: Introducing Git protocol version 2

#20

AIUI, the git ssh protocol is just the git protocol tunnelled through ssh. So why do they need different mechanisms for signalling V2?

Deploying Git over SSH entails locking the precise command line executable by the public key you use to authenticate. Locking SSH SendEnv down is mandatory too, otherwise thousands of people would have shell access to GitHub.com!

This isn't even theoretical, there was an environment-related bug not 5 years ago involving Git. At least BitBucket was impacted, I think GitHub were patched before it was announced

Post reply on HN