Re: [PATCH 1/2] index-pack: Create .keep files with same permissions and .pack/.idx
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 1, 2011, 22:21 UTC
- Message-ID
- <7vk4fdehps.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <AANLkTimMJxni=Vuja+iHyMp8ydm7ZBvWnkSe68g6+pyH@mail.gmail.com>
Shawn Pearce <spearce@spearce.org> writes:
Show 8 quoted lines
> On Fri, Apr 1, 2011 at 17:39, Junio C Hamano <gitster@pobox.com> 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.