Shawn Pearce <spearce@xxxxxxxxxxx> writes: > On Fri, Apr 1, 2011 at 17:39, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> While I am not sure if letting a clone proceed while there is a concurrent >> push is even a good idea to begin with, > > What? Why? > > Are you suggesting that Git hosting sites disable readers while there > is a push occurring? This is an irrelevant comment isn't it? Hosting sites coming via git protocol will not suffer from this "in-progress .keep not readable" issue at all. I was responding to the motivation stated in the commit log message, the file-based "cp -r" copy or cpio clone, which are _not_ a safe thing to do. Because "leftover .keep" alone is a good justification, I was hinting to drop that other motivation from the description altogether. -- 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