If it contains subroutines related only to HTML output, why isn't it
called Gitweb::HTML then? If it contains some subroutines which are
not strictly about HTML, please state it in the commit message.
Whether you use Gitweb::Git or Git.pm, you should be consistent in the
naming you use: either Git.pm, or Gitweb::Parse.
Do I understand correctly trhat Gitweb::Parse and Gitweb::Format are to
be added in subsequent patches? Please state this fact in the commit
message.
Nitpick: my first thought was "why some of those subroutines are marked
with a star?". If you want to divide this list of subroutines into
groups by function, you should leave a space between '*' and name of
subroutine (i.e. '* href'), and perhaps also leave empty lines between
groups, though this might make commit this list overly long.
I guess that this separation of subroutines into Gitweb::View module
was a matter of some compromise: between having too large modules
(containing only barely related subroutines) and having too many
modules.
I have not checked the diff itself...
--
Jakub Narebski
Poland
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html