Dear diary, on Tue, Jun 20, 2006 at 06:51:18PM CEST, I got a letter where Jakub Narebski <jnareb@xxxxxxxxx> said that... > * Add git fetch URL to the project page from gitweb-xmms2. Needs site-wide > base_url, which need not to be set as there is sane default: use base > of gitweb URL. > > Is it useful to allow repository configuration to override it? Certainly. E.g. http://pasky.or.cz/gitweb.cgi hosts some random projects but generally they are to be fetched from totally different locations. > * Refactor dispatch from if...elsif...else construction > to using 'name' => \&sub hash. In other words, you say the result of the IRC discussion we had about symbol lookups and evals turned out really scary? ;-) > * 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. For Bugzilla, just /\bbug (\d+)/i is frequently used so many people are probably used to it while it feels natural and doesn't make you tumble over it when reading the message. For these things it's simplest to give the user ability to specify some regexp substitutions to be applied on commit messages. About sha1 turned to references, I don't think that's practical until you will have some way of finding out whether a given sha1 is a valid object reference without Theta(n) forks. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ A person is just about as big as the things that make them angry. - : 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