Re: vc-git bug with top-level repositories

[Alfred M. Szmidt]

   >> How about adding an extra check, where we check the write permissions
   >> as well for the user and group?  That is, if the user and the group
   >> the user is member of, cannot write to the .git directory then we stop
   >> traversing...

   >    I don't think this will fly: currently VC works even when you're looking
   >    at a project to which you don't have write access, so neither the files
   >    nor the .git might be writable.

   > AFAIK, atleast for git, you must have write access, if you do not you
   > cannot ceate a lock file.

   So you need write access even just to do things like diff or even
   just diff-index?  That's too bad.  So maybe for Git we could use that
   refinement of my heuristic, but it wouldn't help for other backends.

I think for git diff you do not need write permissions, since that
doesn't need to be atomic.  I know that for some commands you need
write access (git status comes to mind).