…

Another thing that makes my transition impossible is the limited hosting possibility on Windows .. and I have some Windows guys in teams of my few project – they refuse to use a DVCS that cannot be hosted properly on Windows, even though they can happily use it as a client. I guess everybody has his pride.

Sorry for my rant but what I hope to get is some answers why things are the way they are and why is it not changing?

Cheers

1. It’s not displaying this blob correctly: http://cgit.kde.org/amarok/amarok/tree/README (”plain” works)

Do you have a copy of the generated html? It sounds like some error occurred while generating the reply, and if so the html would lack closing tags. Also, the httpd errorlog generated at the time of the incident might prove helpful.

2. It’s showing a bogus diff for this merge commit (while git show, Redmine, Gitorious and gitweb show none, as expected): http://cgit.kde.org/konversation/konversation/commit/?id=7d1cb2fae86290da76ee0d0ded602c777f6e0ac8

This is a known issue in cgit – it shows diffs against the first parent instead of the (usually empty) merge conflict diff. A proper fix for this requires some extensions to git.git, but a quickfix is just to disable diffs for merge commits. I’ll add a cgitrc-option for the latter, and try to extend git.git with the needed callbacks to show proper combined diffs in cgit.

3. The caching appears to be wonky in practice, e.g. with caching enabled it won’t update the Branch table on the “summary” page to show the actual latest commit.

I’ve seen similar behavior when the cgit process has lacked permissions to replace cache files (e.g. if the cgit binary had previously been invoked from the command line). When processing a request, cgit will favor fast serving of stale cache entries when a concurrent request has already locked the selected cache entry.

A copy of the cgitrc-file used in the setup of cgit.kde.org and the httpd errorlog for the period when you discovered these problems might help me debug/fix these issues.