On Tue, 19 Jul 2011 20:33:23 +0530 Sitaram Chamarty <sitaramc@xxxxxxxxx> wrote: > On Tue, Jul 19, 2011 at 4:40 PM, J. Bakshi <joydeep@xxxxxxxxxxxxxxx> wrote: > > > Just like git-receive-pack anything for git pull,clone etc.. ? then we can use those to restrict read access separately. Users having read access need not have the right access then. > > git-upload-pack I guess. Maybe git-upload-archive also. > I have tried with git-upload-pack, but it gives error as ```````````` Cloning into .... error: RPC failed; result=22, HTTP code = 401 fatal: The remote end hung up unexpectedly ```````````````` The configuration I use is ```````````` <LocationMatch "^/git/.*/git-upload-pack$"> AuthType Basic # Message to give to the committer AuthName "Write access requires a password" # File listing users with write (commit) access AuthUserFile /home/git/pushACL Require valid-user </LocationMatch> ```````````` -- 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