Well, I try to either save interesting gitweb patches (which doesn't help
much), or import them to my repository at
The interesting branches would be gitwe/* branches. Some of them are
regularly rebased against 'master' branch of main git repository.
Those branches are:
The branch that I am doing miscelanous gitweb development on. Managed
using StGit, not all patches applied (visible). Regularly rebased
against 'origin' branch.
Currently contains syntax highlighting support from Johannes Schindelin
(based in turn on Daniel Svensson's and Sham Chukoury's work in
gitweb-xmms2.git), plus my refactoring of that.
Needs decision on names of subroutines, and on semantics of 'highlight'
feature (on/off, or highlighter name).
Simple file-based output caching for gitweb, based on work by John
'Warthog9' Hawley (J.H.), split into smaller patches for easier review.
Much more configurable than original patch(es) by J.H., with pluggable
caching engine (it works for example with Cache::FileCache).
J.H. ideas were: no serialization and mtime based expiration of simple
file-based cache, using locking to avoid 'cache miss stampede' problem,
serving stale data when cache entry is being regenerated, generating
cache in background, trick for non-AJAXy progress info, having everything
related to cache in 'cache.pm' file.
My ideas were: tests, separating simple file-based cache into separate
package and making it easy to replace this cache engine by any
Cache::Cache or CHI cache driver, select(FILEHANLE) based capturing,
separating capturing output into package to be able to replace it by
other captyring mechanism, daemonizing for background cache generation
(for mod_perl), being able to 'require' the 'cache.pm' file, gathering
options in %cache_options and adding configurability, documentation.
This is work in progress, and a bit of mess ...