On Thu, 2011-03-17 at 16:41 +0100, Jakub Narebski wrote: > Drew Northup wrote: > > > I'm obviously a moron because I didn't to bother to scroll through the > > whole thing first. I'm just not going to fight with you. > > I'm going to crawl back under my rock now. > > I came to strong; I am very, very sorry about that. We are really > interested how we can make existence and use of gitweb config file > more obvious. > > The "Build time configuration" section in gitweb/INSTALL is > unfortunately after the one-page fold, so that's probably why > you didn't notice that. It was probably pushed out by changes > in previous section. > > What were your changes to gitweb.cgi script, i.e. where in gitweb > sources we should add notification about build time and runtime > gitweb configuration? Jakub, I'll have another look soon, perhaps this weekend depending on when I'm done my other obligations. At the very least I'm considering making a man page for the configuration file. I don't know off-hand how much that will be seemingly repetitive of the README, but I suspect I'm not the only one who often finds monolithic files tucked away in /usr/share/doc (/usr/doc for some systems) a daunting reading prospect when I really don't care about the project history since 1937 (which, all too often, was the apparent perspective taken when writing the README). I don't think the gitweb README rises quite to that level, but I do think that benefit may be drawn from doing to it what has been proposed for the rest of gitweb--making it into smaller digestible chunks. I don't plan on bothering anybody here about that until I've had a chance to make a mess in my own repo hacking it to pieces for a while. -- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- 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