{"thread":{"id":"14091","subject":"gitweb: Broken links in blame view","startedAt":"2008-06-22T21:37:37Z","lastAt":"2008-06-22T21:37:37Z","messageCount":1,"participants":["Lea Wiemann"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"80645","messageId":"485EC621.7090101@gmail.com","threadId":"14091","inReplyTo":null,"subject":"gitweb: Broken links in blame view","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-06-22T21:37:37Z","receivedAt":"2008-06-22T21:37:37Z","isPatch":false,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"Hi!\n\nI (or rather, the link checker) has discovered another broken link, this \ntime in gitweb's blame view, which happens if you blame files and it \ntries to get parents before the initial (first) commit in the repository:\n\n1. Unpack test.git.tar.gz (attached) into gitweb's project root.\n\n2. Make sure $feature{'blame'}{'default'} = [1]; is on in\ngitweb_config.perl.\n\n3. Open the following page:\nhttp://localhost/.../gitweb.cgi?p=test.git;a=blame;f=file;h=f8c58d2c88cbcf660f473f8f123ee32db0d0d2be;hb=HEAD\n\n4. Click the gray \"1\" line number -- you get a \"400 - Invalid hash base \nparameter\" response (or '403' instead of 400 if you're not on next).\n\n(I've also reproduced this with gitweb revisions from 7 months ago, so \nit's not related to recent changes.)\n\nAlso, probably related, if you open the above blame view by calling \ngitweb.cgi on the command line, you'll see a bogus error message on \nSTDERR: \"fatal: ambiguous argument 'f891e539f...^': unknown revision\" \nNote that f891... is the earliest revision in the repository.\n\n-- Lea\n"}]}