Hi, Here is another issue with gitweb integration which i think might be considered as a feature proposal: I have a central place where bare repos are. They're owned by the user under which we are serving them, let's say “git”. So, gitweb is going to show me Repo1 owner git etc… In order to show a real owner I have to rebuild gitweb.cgi, to tell it to use the file for GITWEB_LIST and edit the file… In fact I think gitweb shouldn’t carry this info, but bare repos should. So my idea is: Either provide a key to $ git clone –bare –u “owner/email” or take the user.email parameter from .gitconfig. in both cases the info can go to description file of bare repo, so it can look like: $owner=owner@xxxxxxxxxx $description=”very long description” Or in xml form… Yes, description file might become a bit more complicated in its layout. But, the benefits are obvious: - No need to support multiple lists/files - Bare repo carries all info about itself (together with –d feature I described earlier). I this circumstances gitweb’s GITWEB_LIST will be only filter (only repo path is necessary to show/not show), and it seems that narrowed functionality here is a good thing... Your thoughts? Thanks, Eugene -- 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