On 20 July 2016 at 23:35, CLOSE Dave <Dave.Close@xxxxxxxxxxxxxxxxxx> wrote: > Thanks, Jakub, for the quick response. > > On 07/20/16 02:20 PM, Jakub Narębski wrote: > >>> If I replace the hb=SHA argument with hb=HEAD, the URL still works. But >>> I have no idea what I can use to replace the h=SHA argument. >> >> You can remove it. 'hb' (hash_base) and 'f' (filename) identify target >> file in a repository unambiguously. > > If I do, leaving everything else present, I get "404 cannot find file". Which gitweb version are you using? For 'a=blob' (i.e. displaying contents of the file), if 'h' (hash) parameter is not set, then gitweb finds it by using `git ls-tree <hash_base> -- <filename>` in git_get_hash_by_path() subroutine. No 'hb' is equivalent to 'hb=HEAD' What does `git ls-tree <hash_base> -- <filename>` results in your repository? >>> A complication is that the target file is not in the master branch. >>> Somehow I need to be able to specify the branch. I've tried putting it >>> as the h= argument but that results in "Reading blob failed". If I leave >>> out the h= argument entirely, gitweb responds, "404 cannot find file". >> >> Did you forgot to set 'hb' parameter? Is said file present in revision >> given by the 'hb' parameter? > > The file is present in both master and develop branches. If I include > hb=HEAD and leave out h=, gitweb doesn't find either of them. It works for repo.or.cz (which uses gitweb as web interface). So we have WORKSFORME situation. Now we need to find out what is different in your case... > Using > hb=HEAD and h=develop or h=master results in "Reading blob failed". 'h' must be hash of the blob as an abject (of its contents at given revision). -- Jakub Narebski -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html