Timur Tabi <timur@xxxxxxxxxxxxx> writes: >> If you provide access for others, i.e. if those repositories shown in >> gitweb are public repositories, it is much better to use bare >> repositories for that. > > Why? What difference does it make if they clone directly from my > working tree, instead of some shadow repository? There is none. Even though I would not personally publish the live repository I personally work in via gitweb, I do not think that has to be a holy rule not to be broken by anybody. Some people may want to show state of a live tree, and other people may be willing to peek into it. I do not think it is worth spending excess effort beyond giving one educational advice like Jakub did to prevent them from doing so. It's their choice. While they may have to live with the consequence of such an arrangement, other people won't be harmed (I do not think it is such a big deal for them to deal with the fallout either). I personally would not mind peeking into such a gitweb, but I would really hesitate to fetch from a repository that is known to be live. The commits I would see there right now are not likely to be in the finished form (the live repository owner may want to amend them). The repository owner may promise "I'll keep them stable and never amend", but that is worse, at least from my point of view, as nobody is perfect and the resulting history in such a live repository is bound to be full of crufts I'd rather not have to wade through. It is a very useful coalmine canary to see the path in gitweb ending with slash dot git like /home/tt/foo/.git, not /home/tt/foo.git, for me to be able to tell which is which. If it is a bare repository without a work tree, as long as the repository owner has graduated the CVS mentality and acquired a good habit of not pushing things too hastily, there is a chance that the history I would see there is reviewed by the author and cleaned up to be presentable. -- 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