Hi, Somebody from development camp recently complained here that there is no many end users "chiming" about issues in the mailing list. Well, don't tell i didn't try;) First I tried to use gitweb.url, gitweb.description and gitweb.owner files and none of them worked... gitweb is unable to pickup the info from those files. Although it successfully interactively picks up info from description and cloneurl files. I didn't find a substitution for gitweb.owner... I might be sent to RTFM again, but i would like to bring an attention to the fact that setting up bare repo with these simplest parameters as well as setting up gitweb is a USABILITY NIGHTMARE for beginners. I would even say more: while gitweb is very flexible and powerful, all its flexibility and power is hidden behind unusable management interface, which IMHO requires a lot of improvements . Rebuilding to configure? Perl look-and-feel for configuration variables? I think this is not the way to configure web applications no matter how smart and flexible application should be. There are some problems with XML, I don't care. Let's use simple property file. 1 property file! and let gitweb read it. don;t like this solution, propose yours.. But leaving the emotions aside and once again - On Sun, 11 Oct 2009, Jakub Narebski wrote: >And this would be best left for a custom script creating repositories >and their git hosting related configuration. Such script of necessity >would have to be site-specific, or at least contain site-specific >configuration, like: >* whether to use gitweb.owner or filesystem uid + GECOS is enough >* whether to use gitweb.description or description file >* whether to use gitweb.url, cloneurl file, or let gitweb autogenerate >clone / fetch URL from base URL I don't get it. I'm talking specifically about gitweb bundled into git package by default. It was bundled as i understand to provide full solution (I don't see any other reason). What the heck is wrong with continuing to move in this direction? I'm not talking about to enforce gitweb usage, but just simplify the setup and configuration of a tool provided by default... If the user chooses default solution, what is wrong with providing some usable way of doing things? Don't want to use git clone, fine. But, please, please save me from rebuilding gitweb, creating manually those files and putting info inside... It is 21st century or what?;) >* gitosis / gitlite configuration, if needed, or setup of public keys >for SSH authentication Are they included into git bundle? I didn't see those tools there... >* project README.html file, if used >etc. Yes, I might be stubborn, but is just because i feel that i can contribute into making git better, although I'm not a developer. And i think usability is the thing which all beginners would thank you for... i understand that this issue is not the end of the world and i will finally overcome the burden, i will develop my script and stuff, I hope somebody would support me in this:) 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