You 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

You 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.