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

Git 1.8.0

raw.github.com

Post reply on HN
Print view View original

11–20 of 54 posts

Re: Git 1.8.0

#11

Post by alpb »

That's great, guys using Homebrew can get this version by writing these:

    brew update
    brew upgrade git

Re: Git 1.8.0

#13

Post by aneth4 »

> "git branch --set-upstream" is deprecated and may be removed in a relatively distant future. "git branch [-u|--set-upstream-to]" has been introduced with a saner order of arguments.

It would be great if changes to the git CLI were thoroughly thought through instead of one-off fixes like this. This is the reason the interface is such a mess.

  git branch foo --track origin/foo
But if you forgot --track:

  git branch foo
then it's:

  git branch foo --set-upstream-to origin/foo
and don't you dare do

  git branch --set-upstream-to origin/foo
Upstream and track are the same - why two different words?

And now we have --set-upstream-to and --set-upstream, which will be fun for git newbies to distinguish.

Re: Git 1.8.0

#14

Post by xentronium »

hack_edu wrote: post #4

> In the next major release (not this one), we will change the behavior of the "git push" command. So wait, is that in this release or not? Why put this at the very most top part of the file without even mentioning what release it will actually be in?

Deprecation notice, I guess:

    "git push" will warn about the upcoming change until you set this 
    variable in this release.

Re: Git 1.8.0

#17

Post by wahnfrieden »

Daniel_Newby wrote: post #16
wahnfrieden wrote: post #10

Earlier quoted context omitted.

I don't know, but it's not meant for hosting pages or page resources unless you use their "pages" feature, so they set it pretty low.

Didn't Github suffer a DoS attack in the past few days?

Yea, these notices under light load are nothing new though.

Re: Git 1.8.0

#18

Post by reitzensteinm »

Zash wrote: post #3

You're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions.

I'm surprised they don't exempt high profile public projects from limits like that. Git being hosted on Github is hugely beneficial to their image.

Any roadblocks should be eliminated for VIPs, especially if the consequence is just a few bucks more in bandwidth bills.

Re: Git 1.8.0

#19

Post by jorde »

wahnfrieden wrote: post #10
Brajeshwar wrote: post #9

btw, what is Github's rate limit?

I don't know, but it's not meant for hosting pages or page resources unless you use their "pages" feature, so they set it pretty low.

Based on headers the limit is 100 requests (per hour if the same as API).

Re: Git 1.8.0

#20

Post by nodesocket »

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
Post reply on HN