After some study about the insertion of a new repository configuration, which sets repository owner, it was decided by the group that creating another small file inside .git/ is not a good idea. So I started to bench the viability to add just the gitweb.owner configuration, using gitweb.owner together with gitweb.description there is no major performance downgrade compared to $projects_list , as seen below: 8<------- These times i got with a 1000projects running 2 dd to generate disk IO. Here comes the resultm NO projects_list projects_list 16m30s69 15m10s74 default gitweb, using FS's owner 16m07s40 15m24s34 patched to get gitweb.owner 16m37s76 15m59s32 same above, but without gitweb.owner Now results for a 1000projects on an idle machine. NO projects_list projects_list 1m19s08 1m09s55 default gitweb, using FS's owner 1m17s58 1m09s55 patched to get gitweb.owner 1m18s49 1m08s96 same above, but without gitweb.owner 8<------- The idea of creating only the gitweb.owner can be a case of study to centralize all gitweb repository configuration in one file. Maybe even change the way $projects_list is formated, as gitweb.cgi needs to check repository configuration to get repository description to generate projecT_list page, we could just list repository's directories. - 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
