Chris Packham <judge.packham@xxxxxxxxx> writes: > On 17/09/11 14:29, Jeff Epler wrote: > > Some time ago I hardcoded this into gitk for $DAY_JOB and find it very > > useful. I made it configurable in the hopes that it might be adopted > > upstream. (unfortunately, the configurable version is radically > > different from the original hard-coded version, so I can't say this > > has had much testing yet) > > This is definitely something folks at my $dayjob would be interested in. > We've already done some customisation of gitweb to do something similar. > I'm not actually sure what the changes where or how configurable they > are. I'll see if I can dig them out on Monday someone else might want to > polish them into something suitable (I might do it myself if I get some > tuits). That would be nice. So called "committags" support was long planned for gitweb, and even some preliminary work exists... > > There are probably better names for the configuration options, too. > > It'd be nice if the config variables weren't gitk specific. .re and .sub > could be applied to gitweb and maybe other git viewers outside of > gig.git might decide to use them. My bikeshedding suggestion would be to > just drop the gitk prefix and have linkify.re and linkify.sub. Perhaps more descriptive name, i.e. linkify.<name>.regexp linkify.<name>.subst would be better? I guess that regexp is an extended regular expression, isn't it? -- Jakub Narębski -- 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