On Sat, Sep 21, 2019 at 2:18 PM Segher Boessenkool <seg...@kernel.crashing.org> wrote: > > On Thu, Sep 19, 2019 at 03:29:27PM -0400, Jason Merrill wrote: > > I suppose we also need to decide what form we want to use for the > > equivalent of gcc.gnu.org/rNNNNN. I figure it needs to be some prefix > > followed by a "commit-ish" (hash, tag, etc.). Perhaps "g:" as the > > prefix, so > > > > gcc.gnu.org/g:HEAD > > gcc.gnu.org/g:gcc-9-branch > > gcc.gnu.org/g:3cf0d8938a953e > > Hrm, but we should probably not allow everything here, some things can > be expensive to compute (HEAD~123456 for example), and we don't want to > expose the reflog on the server (if there even is one), etc. OTOH > allowing pretty much everything here is a quite neat idea. > > What do we use for gitweb thing? That might have a solution for this > already. Currently we seem to use plain gitweb, maybe cgit or similar > would be nicer? It looks more modern, anyway :-P
The current gitweb allows all of my examples with a bit longer URL, e.g. https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3cf0d8938a953e it doesn't seem to allow HEAD~1 or HEAD^. It does allow HEAD@{2}, but I don't see what the problem with that would be. I was figuring to just rewrite the /g: pattern into the appropriate query URL for the git web interface. I have no opinion about which web interface to use. Apparently there are many: https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Web_Interfaces Jason
