This is the nest of gitweb development. If you enjoy hacking gitweb or having the latest and best gitweb on your site, this repository might be interesting for you. This site (repo.or.cz) itself usually demonstrates all the patches at work.

The branches are organized in a very similar way to Git itself. The most notable difference is that they are actually regular TopGit feature branches, thus their history is a little *ahem* wild (but never rewinds).

The meaning of the branches:

• master - gitweb patches that should be good to go straight to git's master; mostly bugfixes
• next - patches for new features that might have seen some review on git@ and could be ready for general usage; includes all the master patches
• pu - patches for experimental features that are somehow usable but might have large nits and/or are still undergoing major development; includes all the next patches; repo.or.cz usually runs on pu, possibly with some patches reverted
• girocco - patches for repo.or.cz-specific features; ideally, this branch would be empty...
• lw-caching, templating - staging branches for larger features that are not even pu-ready yet
• t/* - interdependent TopGit feature branches, each one corresponding to a single patch for upstreaming
• mob - non-volatile branch that is supposed to be tracking git's (not gitweb's) master, open for pushing from anyone; please announce your pushes on git@vger.kernel.org; good patches will be cherrypicked

If you clone this repository, you should have git.git itself as 'vanilla' remote in order for TopGit to work correctly.

If you are active gitweb developer and want push access, please tell me (pasky).