On Tue, Mar 1, 2011 at 3:30 PM, Chad Joan <chadjoan@xxxxxxxxx> wrote: > On Tue, Mar 1, 2011 at 3:08 PM, Jeff King <peff@xxxxxxxx> wrote: >> But it just seems horribly broken to me. This is CIFS to an OpenVMS >> machine you said? Do the broken permissions appear to other clients or >> across a remount (i.e., is it broken state in your CIFS client, or has >> the server actually munged permissions)? If so, have you tried reporting >> the issue to whoever writes CIFS server on OpenVMS (is it just samba)? >> >> -Peff >> > > Yep, CIFS to OpenVMS. > > I don't know about other clients because there are none (yet). ÂThe > permission change does survive remounting. > > I haven't reported it. ÂI didn't know it existed until now ;) > > I'll do that, but it will probably take a long long time for me to see > the patch. ÂI'm hoping there's some cheap hack I can use to work > around it in the meantime. A simple answer to preventing git from calling rmdir would be to run rm and git rm separately: $ rm file $ git rm --cached -f file But that doesn't solve the misbehavior of git under the previous scenario. I'm not sure if this is something we should fix in git or if it should be fixed in cifs. -- 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