On Tue, 16 Jul 2013 10:30:48 -0400
wor...@alum.mit.edu (Dale R. Worley) wrote:

> > > now, can i create a user that can only pull?
> > > that would be great
> > 
> > There's no way to do implement this using plain Git.
> If a user can only *read* the files in the Git repository, what can
> the user do with the repostiory using Git?

May be you're right but may be not -- if Git sets up some king of lock
on the repository to have the consistent view of it while calculating
the set of objects to transfer to the remote side, then fetching won't
work.  I don't know if Git does that and I'm lazy to check.

I admit I had a knee-jerk reaction to the OP's question: if one asks
for fine-grained access control to Git repos my immediate reaction is
to tell that person to look for a specialized solution.  For instance,
gitolite work OK for what I have at my $dayjob.

But you made me look at this problem from a different angle: if this
fits the OP's task, he could just set up a git-daemon instance to
provide read-only access to his repositories.  The obvious downside is
that this method does not provide authorization control as all the
access is anonymous.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to