On Sun, 11 Oct 2009, Eugene Sajine wrote: > > > > The project description, project owner and (clone) url are used by > > gitweb only, so I don't see why git-clone has to feature-creep to > > set them. > > Well my logic is simple. Gitweb is a part of git bundle. If you don't > want to use gitweb you're free to use git clone as you want. I don't > see why not to provide some usability features to it. For me it is > quite obvious that it will be more comfortable to setup gitweb if this > would be in place. Instead of putting info in few different places > manually, why not to give people a possibilty to do that using one > command? > > This is usability feature, but i feel that for me as a person who will > support big ceantral bare repo hosting server, this would save huge > time and efforts... 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 * gitosis / gitlite configuration, if needed, or setup of public keys for SSH authentication * project README.html file, if used etc. git-clone is not a dumping ground (also, code speak louder than words). I even think it might be mistake to have default 'description' file in templates... -- Jakub Narebski Poland -- 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