{"thread":{"id":"42534","subject":"`man 1 git`: Invalid link to online documentation","startedAt":"2016-06-06T03:59:00Z","lastAt":"2016-06-08T12:43:57Z","messageCount":4,"participants":["Daniel Campbell","Jeff King","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"288404","messageId":"ed8f000f-b8a2-ca92-e0f2-e26ff9928bbe@gentoo.org","threadId":"42534","inReplyTo":null,"subject":"`man 1 git`: Invalid link to online documentation","fromName":"Daniel Campbell","fromEmail":"zlg@gentoo.org","sentAt":"2016-06-06T03:59:00Z","receivedAt":"2016-06-06T03:59:00Z","isPatch":false,"sender":{"key":"zlg@gentoo.org","avatar":null},"body":"In `man 1 git`, the Description section outlines an address to\npre-generated documentation [0]. That link returns a 404 error. Playing\naround, I found the repository at [1] and found that it hasn't been\nupdated since August 2015. Given that 2.8.3 is more recent than that, it\nseems like this is something that should be updated (if the\npre-generated docs still exist somewhere) or removed altogether.\n\nAlso worth considering is Google Code was shut down earlier this year.\nWhile archives exist, it can't be relied upon for future use. The\nclosest approximation I could find that was up to date is [2], though\n[3] is a repository that's even fresher than 2.8.3.\n\nSince I'm not familiar with Git development I figured it was wiser to\nlet you know instead of making a decision on what to do and patching.\n\nI know this is minor but I figured it was overlooked. Thanks for reading.\n\n0: http://git-htmldocs.googlecode.com/git/git.html\n1: https://code.google.com/archive/p/git-htmldocs/\n2: https://git-scm.com/docs\n3: https://github.com/gitster/git-htmldocs\n-- \nDaniel Campbell - Gentoo Developer\nOpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net\nfpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6\n\n"},{"id":"288494","messageId":"20160606231936.GB22756@sigill.intra.peff.net","threadId":"42534","inReplyTo":"ed8f000f-b8a2-ca92-e0f2-e26ff9928bbe@gentoo.org","subject":"Re: `man 1 git`: Invalid link to online documentation","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-06T23:19:36Z","receivedAt":"2016-06-06T23:19:36Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Jun 05, 2016 at 08:59:00PM -0700, Daniel Campbell wrote:\n\n> In `man 1 git`, the Description section outlines an address to\n> pre-generated documentation [0]. That link returns a 404 error. Playing\n> around, I found the repository at [1] and found that it hasn't been\n> updated since August 2015. Given that 2.8.3 is more recent than that, it\n> seems like this is something that should be updated (if the\n> pre-generated docs still exist somewhere) or removed altogether.\n> \n> Also worth considering is Google Code was shut down earlier this year.\n> While archives exist, it can't be relied upon for future use. The\n> closest approximation I could find that was up to date is [2], though\n> [3] is a repository that's even fresher than 2.8.3.\n\nYeah, I think Google Code is out. The git-scm.com page automatically\npulls in released versions of the pages, but not the tip of master\n(which is what the git-htmldocs repository has).\n\nThat repository is hosted at kernel.org and at GitHub, so either of:\n\n  https://git.kernel.org/cgit/git/git-htmldocs.git/plain/git.html\n\n  https://raw.githubusercontent.com/gitster/git-htmldocs/master/git.html\n\nbut in both cases the content-type is such that it doesn't render in a\nbrowser (and at least in the GitHub case, that is intentional; we don't\nwant people using their repos directly as a CDN. They should build a\nPages site and push to it).\n\nSo I think the options are basically:\n\n  1. Point to git-scm.com/docs as \"new enough\" as it covers released\n     versions (and lets you walk back to earlier versions, too). People\n     who want bleeding edge can clone htmldocs themselves.\n\n  2. Make git-htmldocs a real site on GitHub. I think this should be as\n     simple as pushing to the `gh-pages` branch of the repository, which\n     would make it available as https://gitster.github.io/git-htmldocs.\n     You can do a bunch of Jekyll magic, but you don't have to; it should\n     serve arbitrary html files (though I think we'd maybe want to add\n     an \"index.html\"; we may also want to host it under a git/htmldocs\n     project just to make the repo more official looking).\n\n  3. Publish to some other Pages-like service. I don't think kernel.org\n     has one, but it's not like there's a lack of sites you can push\n     static HTML files to. I mentioned GitHub in (2) mostly because\n     Junio already pushes there.\n\n-Peff\n"},{"id":"288496","messageId":"20160606232536.GA23537@sigill.intra.peff.net","threadId":"42534","inReplyTo":"20160606231936.GB22756@sigill.intra.peff.net","subject":"Re: `man 1 git`: Invalid link to online documentation","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-06T23:25:37Z","receivedAt":"2016-06-06T23:25:37Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Jun 06, 2016 at 07:19:36PM -0400, Jeff King wrote:\n\n>   2. Make git-htmldocs a real site on GitHub. I think this should be as\n>      simple as pushing to the `gh-pages` branch of the repository, which\n>      would make it available as https://gitster.github.io/git-htmldocs.\n>      You can do a bunch of Jekyll magic, but you don't have to; it should\n>      serve arbitrary html files (though I think we'd maybe want to add\n>      an \"index.html\"; we may also want to host it under a git/htmldocs\n>      project just to make the repo more official looking).\n\nJust to make sure I wasn't spewing nonsense, I tried pushing the tip of\ngitster/git-htmldocs to the \"gh-pages\" branch of git/htmldocs, and\nindeed:\n\n  https://git.github.io/htmldocs/git.html\n\nnow works. If we like that solution, Junio, you should already have\naccess to just push there (instead of gitster/git-htmldocs, or in\naddition to if you prefer).\n\nIf not, I'll delete the repository (I don't plan on doing further\npushes, so leaving it will just confuse people).\n\nI see that we _do_ have an index.html symlink in the built tree, but it\ndoes not seem to actually work via GitHub Pages.\n\n-Peff\n"},{"id":"288708","messageId":"eeb75a91-17d6-bb49-e4d6-34bf4fb3defe@drmicha.warpmail.net","threadId":"42534","inReplyTo":"20160606232536.GA23537@sigill.intra.peff.net","subject":"Re: `man 1 git`: Invalid link to online documentation","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2016-06-08T12:43:57Z","receivedAt":"2016-06-08T12:43:57Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Jeff King venit, vidit, dixit 07.06.2016 01:25:\n> On Mon, Jun 06, 2016 at 07:19:36PM -0400, Jeff King wrote:\n> \n>>   2. Make git-htmldocs a real site on GitHub. I think this should be as\n>>      simple as pushing to the `gh-pages` branch of the repository, which\n>>      would make it available as https://gitster.github.io/git-htmldocs.\n>>      You can do a bunch of Jekyll magic, but you don't have to; it should\n>>      serve arbitrary html files (though I think we'd maybe want to add\n>>      an \"index.html\"; we may also want to host it under a git/htmldocs\n>>      project just to make the repo more official looking).\n> \n> Just to make sure I wasn't spewing nonsense, I tried pushing the tip of\n> gitster/git-htmldocs to the \"gh-pages\" branch of git/htmldocs, and\n> indeed:\n> \n>   https://git.github.io/htmldocs/git.html\n> \n> now works. If we like that solution, Junio, you should already have\n> access to just push there (instead of gitster/git-htmldocs, or in\n> addition to if you prefer).\n> \n> If not, I'll delete the repository (I don't plan on doing further\n> pushes, so leaving it will just confuse people).\n> \n> I see that we _do_ have an index.html symlink in the built tree, but it\n> does not seem to actually work via GitHub Pages.\n> \n> -Peff\n> \n\nI like that a lot. It makes good use of the existing infrastructure at\ngithub, and the rendering uses screen real estate much better than the\nversion on git-scm.com.\n\nIf Junio integrates it into his usual workflow then we don't have the\nupdate issues that we have over there. Rendered documentation in-sync\nwith the code, hooray :)\n\nMichael\n"}]}