{"thread":{"id":"14439","subject":"Vanilla gitweb vs repo.or.cz","startedAt":"2008-07-13T11:59:30Z","lastAt":"2008-07-13T11:59:30Z","messageCount":1,"participants":["Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"83144","messageId":"20080713115930.GH10151@machine.or.cz","threadId":"14439","inReplyTo":"20080713082812.GA4944@perso.beuc.net","subject":"Vanilla gitweb vs repo.or.cz","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2008-07-13T11:59:30Z","receivedAt":"2008-07-13T11:59:30Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"  Hi,\n\nOn Sun, Jul 13, 2008 at 10:28:12AM +0200, Sylvain Beucler wrote:\n> >   By the way, where can I see the source code of the gitweb you are\n> > using?\n> \n> We're using vanilla gitweb from the official Git, actually.\n\n  ah, of course! Somehow, I forgot that you can customize the project\nURLs shown without modifying the source code nowadays.\n\n> Apparently that version begins to be outdated, doesn't it? For\n> example, a user recently suggested we use a cache for the start page\n> project list but that feature doesn't seem to be merged yet. Maybe\n> should we switch to repo.or.cz's version directly?\n\n  This is a bit more complicated; I've cc'd the Git mailing list in case\nsomeone else finds this informative.\n\n  The upstream gitweb is under active development; most importantly,\nLea Wiemann is intensively working on a new caching infrastructure and\nis doing some cleanups, while Jakub Narebski tries to fight the general\napathy by posting various interesting RFC patches I keep promising\nmyself to finally check out (most importantly for an index page\noverhaul; the recently introduced content tags were the first step\nto this).\n\n  Then, there is the http://repo.or.cz/w/git/gitweb.git repository,\nwhich was my old attempt at maintaining gitweb actively. Unfortunately,\nthis didn't quite work out because of my general lack of time and\ndedication. However, the next and pu branches still contain some patches\nand these patches are actively used on repo.or.cz; I still hope to get\nto clean them up and resubmit sometime soon. I'm working on a certain\nGit-based project essentially fulltime this summer, so I hope to do get\naround to it. :-)\n\n  Finally, there is the http://repo.or.cz/w/git/repo.git repository.\nThis is the Git variant repo.or.cz uses - both for gitweb and the rest\nof Git binaries too (e.g. git-daemon and gc cronjobs; however, I need to\ndo the ssh chroot updates manually, so that might lag a lot behind;\nuntil just a few days ago, Git version in the chroot was from December\n2007).  It dubbles as my personal Git patch queue, but most of the\nnon-gitweb patches aren't generally interesting (and mostly remind me\nof \"what all should I redo differently sometime\").\n\n  The gitweb patches in git/repo.git are superset of git/gitweb.git\npatches and the extra patches are I believe (at least not currently)\ninteresting for general gitweb public. However, some of them _might_\nbe interesting for large-scale gitweb hosting like yours. Some of them\nmight end up in git/gitweb.git after some cleanup (graphiclog link,\nemail addresses obfuscation, ...).\n\n  Thus, my recommendation for now would be to check out the patches\nqueued in\n\n\thttp://repo.or.cz/w/git/gitweb.git\n\thttp://repo.or.cz/w/git/repo.git\n\nand maybe cherrypick some interesting ones; basing your gitweb directly\non git/repo.git probably does not make much sense unless you revert\n\"Custom gitweb changes\" and probably others. Basing your gitweb on\ngit/gitweb.git might work, but would be a little bit adventurous. ;-)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nGNU, n. An animal of South Africa, which in its domesticated state\nresembles a horse, a buffalo and a stag. In its wild condition it is\nsomething like a thunderbolt, an earthquake and a cyclone. -- A. Pierce\n"}]}