Carl Worth wrote: > On Tue, 20 Jun 2006 18:51:18 +0200, Jakub Narebski wrote: >> >> Any further ideas for other useful features? >> > > Since you asked... > > From the first time I saw gitweb the feature I wanted was to put > more useful information in the path of the URL rather than in the > query string. > > One possible organization might be: > > /<project>/<commitish>/<path>[/<more_path> ...] > > I'd really like to be able to publish nice clean URLs (without any > query component) for getting at particular branches within projects, > for example. > > The above might not be entirely feasible in the face of hierachical > project names containing '/' characters as they might then conflict > with branch names. And in the face of topic branches with names like 'js/lsfix' or 'gitweb/config'. Add to that the fact that above needs some support from web server (e.g. Apache's mod_rewrite) and web server configuration, while gitweb tries to be server agnostic... One of the part of HTML cleanup would be changing order of URL query string, so that the human readable part is first. P.S. I have forgot about: * Check how gitweb.cgi behaves with mod_perl, and correct/add modifications to support this mode better (and perhaps also FastCGI if it adds anything). -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - : 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