6 ms·
Git 1.8.0
- patrickod 14y agoAnyone have a mirror? GitHub has stopped serving this as it's over their rate limit.
- josegonzalez 14y agohttps://github.com/git/git/blob/master/Documentation/RelNotes/1.8.0.txt https://github.com/git/git/blob/master/Documentation/RelNote...
- Zash 14y agoYou're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions.
- josegonzalez 14y agoYou can view the text at this link: https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.0.txt https://github.com/git/git/blob/master/Documentation/RelNote... Also note, it is quite easy to transform github urls back and forth. For all text files, there is a `blob` portion that comes after the repository name and before the branch. You can change that to `blame`, `commits`, `edit`, or `raw`. When changing it to `raw`, the user is redirected to the `raw.github.com` subdomain. `blob` is the normal view, and `commits` is a history of the file. Note that using the `edit` version will instantly create a fork in your account for that repo. Resulting in notifications for it, regardless of whether you actually edit it. I guess it's eager forking so that the user doesn't notice this in the foreground. Blech. You can also change the branch name - it is master in this case - to whatever branch you want. Or commit-sha. Or tag. Almost anything tree-ish will work with Github's UI. The cool thing about this is that it also pretty much works for the gist service they provide, which allows you to do stuff like: - create javascript-based inline diffs - show changes across multiple forks of a gist - consolidate commits for a file Pretty hackable.
- ragsagar 14y agohttps://github.com/git/git/blob/8c7a786b6c8eae8eac91083cdc9a6e337bc133b0/Documentation/RelNotes/1.8.0.txt https://github.com/git/git/blob/8c7a786b6c8eae8eac91083cdc9a...
- reitzensteinm 14y agoI'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.
- rtomayko 14y agoWe actually don't care about rate limits with this type of raw request. The limits are in place because people (usually porn sites) hot link js/css/image assets which can lead quickly to an insane number of requests. If file extensions could be used to determine whether a resource could be used like this, we'd only apply the rate limits to those. Browsers don't care about extensions or event content types though. They'll happily use whatever's at the other end of a URL for <link rel=stylesheet>, <script>, and <img> tags. As for whitelisting, it's a path we just don't want to go down for raw requests. We do a lot of that for the API and it isn't cheap to maintain.
- Tobu 14y agoBrowsers will ignore content-type in many cases (html5 embraced that quirk), but they do have to sniff the bytes to confirm their hunch. You could use `file` to detect images. Or use the content length, maybe by changing hit quotas into bandwidth quotas. https://code.google.com/p/browsersec/wiki/Part2#Content_handling_mechanisms https://code.google.com/p/browsersec/wiki/Part2#Content_hand... http://mimesniff.spec.whatwg.org/ http://mimesniff.spec.whatwg.org/
- nicholassmith 14y ago"The limits are in place because people (usually porn sites) hot link js/css/image assets" I'd like to be surprised by that but I'm not.
- chaitanyav 14y agogot the same "You're over the rate limit. Serve this file from your own servers. Contact support@github.com if you have questions."
- ragsagar 14y agoi am able to access the file from that link.
- hack_edu 14y ago> 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?
- josegonzalez 14y agoNo, it is not in THIS release. it is in the NEXT major release. 1.8.0 is the current major release. 1.9.0 (or 2.0.0, whatever) will have the change.
- xentronium 14y agoDeprecation notice, I guess: "git push" will warn about the upcoming change until you set this variable in this release.
- solox3 14y agoThat's a good change. I've never had the need to "git push" an entire repo, and pushing the current branch is simply more natural to do.
- Brajeshwar 14y agobtw, what is Github's rate limit?
- wahnfrieden 14y agoI 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.
- Daniel_Newby 14y agoDidn't Github suffer a DoS attack in the past few days?
- wahnfrieden 14y agoYea, these notices under light load are nothing new though.
- jorde 14y agoBased on headers the limit is 100 requests (per hour if the same as API).
- alpb 14y agoThat's great, guys using Homebrew can get this version by writing these: brew update brew upgrade git
- dfc 14y agohttp://git.kernel.org/?p=git/git.git;a=blob_plain;f=Documentation/RelNotes/1.8.0.txt;hb=8c7a786b6c8eae8eac91083cdc9a6e337bc133b0 http://git.kernel.org/?p=git/git.git;a=blob_plain;f=Document...
- gulbrandr 14y agoThank you.
- aneth4 14y ago> "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.
- makeramen 14y agoWait, what exactly happens in that last one that I shouldn't dare do?
- aneth4 14y agoI should have written: git branch --set-upstream origin/foo This counter-intuitively creates a LOCAL (!) branch named origin/foo which tracks the current branch. I would expect this to set the upstream of the current branch, given that most commands operate on the current branch unless otherwise specified. Instead it does something completely unexpected and useless.
- ibotty 14y agowhich invalidates part of your point, because --set-upstream is now _deprecated_.
- aneth4 14y agoIt'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?
- nodesocket 14y agoSeems 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
- netshroud 14y agoX-RateLimit-Limit? Sounds redundant.
- riffraff 14y agomaybe they meant to have X-RateLimit-reset-at X-RateLimit-remaining etc, so X-RateLimit- works as a sort of namespace.
- technoweenie 14y agoThey're the same headers the Twitter API uses: https://dev.twitter.com/docs/rate-limiting/1.1 https://dev.twitter.com/docs/rate-limiting/1.1
- vinitool76 14y agoIs updating worth it?
- isarat 14y agoI really wish a day when I am able to download the code with minimal footprint. (few previous versions).
- Osiris 14y agoWhy in the Release Notes do they use the verb "learned" to describe adding a command line option to a feature? "git cherry-pick" learned the "--allow-empty-message" option It's not like Git has obtained sentience and has started to teach itself new tricks, though that would be an interesting development. I understand what they are trying to say I just thought the choice of verb and subject was odd, leaving out the developers as those acting on the code.
- derleth 14y agoDevelopers often anthropomorphize things to gloss over irrelevant details. The focus is on what, not how, and anthropomorphizing is the quickest route to get that across.
- peff 14y agoWriting it in the passive voice is slightly more awkward. E.g., "git cherry-pick" was enhanced with an "--allow-empty-message option". Similarly, writing it in the active voice but attributing the verb properly ends up with meaningless words: "Developers taught cherry-pick to..." or "We taught cherry-pick to...". Every entry would begin that way; having the first words be the relevant subsection of git makes it easier to skim through the release notes.
- malkarouri 14y agoI would have gone for "git cherry-pick" acquired the "--allow-empty-message" option or "git cherry-pick" now has the "--allow-empty-message" option myself. I think the subject is fine with the emphasis where it belongs. The verb is weird, though.
- manojlds 14y agoDoes someone have more info on this: A credential helper for Win32 to allow access to the keychain of the logged-in user has been added.
- mrnil 14y agoYou can find it in contrib: https://github.com/gitster/git/tree/master/contrib/credential/wincred https://github.com/gitster/git/tree/master/contrib/credentia... See man 7 gitcredentials on how to set it up.
- messel 14y agolooking for saner nested submodule pulling , reading now
- urza 14y agoCan git work with subtrees yet?
- xyz-x 14y agoAwesome, now when and where do I download it for Windows??? "Please checkout the source and build it yourself" - wtf.