Live data from Hacker News

Git 1.8.0

raw.github.com

51–54 of 54 posts

Re: Git 1.8.0

#51

Seems to be back up. I assume they waived the rate limit. curl --head https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.0.txt HTTP/1.1 200 OK Server: nginx Date: Mon, 22 Oct 2012 05:32:02 GMT Content-Type: text/plain; charset=utf-8 Connection: keep-alive Status: 200 OK X-Runtime: 14 X-RateLimit-Limit: 100 Content-Length: 1 X-Frame-Options: deny Cache-Control: no-cache X-RateLimit-Remaining: 100

X-RateLimit-Limit? Sounds redundant.

They're the same headers the Twitter API uses: https://dev.twitter.com/docs/rate-limiting/1.1

Re: Git 1.8.0

#52
post #46

Awesome, now when and where do I download it for Windows??? "Please checkout the source and build it yourself" - wtf.

As a windows user, you should know by now that you are a second class git user. You'll have to wait.

Re: Git 1.8.0

#53
post #40
post #38

Earlier quoted context omitted.

It's deprecated in the next release not this one, and it will be around for years to come. People will google and find the old way documented and have to read up on the difference, adding to the cognitivie baggage of git. Regardless, my point is the interface is horrible and this is just adding to the patchwork. Why not add --track semantics or unify these flags?

--set-upstream is deprecated in this release.

Deprecated, but not removed yet. It "may be removed in a relatively distant future"

Re: Git 1.8.0

#54
post #40

Earlier quoted context omitted.

--set-upstream is deprecated in this release.

Deprecated, but not removed yet. It "may be removed in a relatively distant future"

This is what deprecated means. You can't just remove an API that's existed for years and scripts may depend on without giving them time to adapt. This shows a warning when it's used so it's clear which scripts should be changed.
Post reply on HN