Junio C Hamano wrote: > Jakub Narebski <jnareb@xxxxxxxxx> writes: > >> I have very preliminary work, where gitweb uses @enabled_committags as list >> of committags to use, and %committags_info for actual committags info. >> Examples of committags includes current linking of commit sha1, >> gitweb-xmms2 linking of BUG(n) and FEATURE(n) to site-wide based URL >> (Mantis), and RELEASE x.y.z to site-wide based URL (Wiki); perhaps "bug n" >> to site-wide/project-wide URL (Bugzilla)... any other ideas? > > Use a regexp as %committags key and its value to be whatever > that takes the matched string and munge it into a URL form > perhaps? A site that does not have commit tags do not have any > element in that hash. The problem is when you have a bunch of projects, all server by the same gitweb, but otherwise unrelated, so needing different committags (e.g. one project uses Mantis and needs "BUG(n)" and "FEATURE(n)", another uses Bugzilla and needs "bug nn", yet another doesn't use any bugtracker). And for committag you would want also information if to use it in summary (title) in shortlog, head, history etc. views. But this might be a good idea. We loop over all enabled (active) committags. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: 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