Giuseppe Bilotta wrote: > Fourth version of my gitweb PATH_INFO patchset, whose purpose is to > reduce the use of CGI parameters by embedding as many parameters as > possible in the URL path itself, provided the pathinfo feature is > enabled. A nit: when sending longer patch series you should use numbered format in the form of [PATCH m/n] or [PATCH m/n vX] prefix. > > The new typical gitweb URL is therefore in the form > > $project/$action/$parent:$file..$hash:$file > > (with useless parts stripped). Backwards compatibility for old-style > $project/$hash URLs is kept, as long as $hash is not a refname whose > name happens to match a git action. Minor nit: there was also old-style $project/$hash_base:$file_name path_info format. > > The main implementation is provided by paired patches (#1#3, #5#6) > that implement parsing and generation of the new style URLs. > > Patch #2 deals with a refactoring of the input parameters parsing and > validation, so that the rest of gitweb can be agnostic wrt to the > parameters' origin (CGI vs PATH_INFO vs possible other future inputs > such as CLI). > > Patch #4 is a minor improvement to the URL syntax that allows web > documents to be properly browsable in raw mode. Very nice summary of patchset and patch coverage in this cover letter. > > Giuseppe Bilotta (6): > gitweb: parse project/action/hash_base:filename PATH_INFO > gitweb: refactor input parameters parse/validation > gitweb: generate project/action/hash URLs > gitweb: use_pathinfo filenames start with / > gitweb: parse parent..current syntax from pathinfo > gitweb: generate parent..current URLs -- Jakub Narebski Poland -- 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
