Jakub Narebski <jnareb@xxxxxxxxx> writes: > I am planning on copying features from xmms2's gitweb version > to git's gitweb, and introducing new ones. > > Which of those should be implemented first? Clean-ups and obvious fixes without introducing new features first please. > * Add (of course optional, like blame support) snapshot support. There are > at least two different implementations. I'd prefer to do without second > CGI script, but perhaps this is better from the performance point of view. > gitweb-xmms2 has snapshot.cgi in Python: should it be rewritten in Perl? Isn't it just the matter of spawning git-tar-tree? > * gitweb-xmms2 has something called committags support: it means that > 'BUG(n)', 'FEATURE(n)' and 'RELEASE: xx' in commit message are turned into > bugtracker (Mantis for xmms2) or wiki links. It is extension of turning > sha1-ids into references. Probably needs some extra configuration file, > and some per repository configuration. Of course we want to support not > only Mantis, but also e.g. Bugzilla (e.g. Linux kernel) and conventions > for marking bugs therein. Yes, I found this quite nice. BTW, are you in touch with xmms2 folks? - : 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