Hi,
On Sep 25, 2008, at 11:30 AM, Jakub Narebski wrote:
* Support for FastCGI (via CGI::Fast or FCGI).
Unfortunately I don't use FastCGI. This has to be done in a very
un-intruisive way, and without performance penalties for "ordinary"
CGI and mod_perl.
Suggested: input reading and validation refactoring.
Is it ok to require CPAN modules? If yes, then using HTTP::Engine as a
base could be helpful here.
It supports standalone deployments as well as FastCGI, CGI, mod_perl,
POE and others.
And it acks as a very simpe HTTP-layer, without any "framework" logic.
* Committags support
Support expansion of "tags" in commit messages, like gitweb now
does for
(shortened) SHA-1, converting them to 'object' view link. It
should be
done in a way to make it easy configurable, preferebly having to
configure only variable part, and not having to write whole
replacement
rule.
Possible committags include: _BUG(n)_, bug _#n_, _FEATURE(n),
Message-Id, plain text URL e.g. _http://repo.or.cz_, spam
protecting of
email addresses, "rich text formatting" like *bold* and _underline_,
syntax highlighting of signoff lines.
If this part is modular, we can even use a full blown text markup
tool, like Markdown or Textile, to generate the HTML version of the
commits.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo@xxxxxxxxxxxxxxxx
Use XMPP!
--
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
