On Thu, Jun 30, 2011 at 01:14:49PM +0200, Tino Schwarze wrote:
> Of course, this makes using Subclipse et al a bit cumbersome since you
> cannot just browse the repo. It would be nice to have non-recursive
> rights - that way, I could grant "r" to / and /customerA to theguy and
> he would be able
Hi Bob,
On Wed, Jun 29, 2011 at 02:15:39PM -0400, Bob Archer wrote:
> > Given the following structure:
> >
> > /customerA/projA/
> > /customerA/projB/
> > /customerA/projC/
> > ...
> > /customerB/projX/
> > /customerB/projY/
> > ...
> >
> > Is there an easy way to grant someone rw-access to /cus
> Given the following structure:
>
> /customerA/projA/
> /customerA/projB/
> /customerA/projC/
> ...
> /customerB/projX/
> /customerB/projY/
> ...
>
> Is there an easy way to grant someone rw-access to /customerA/projB
> *only*, that is without something like the following in authz?
>
> [/]
> th
Try it and see?
(and btw you may not need the theguy=r record on the root dir)
Tino Schwarze wrote on Wed, Jun 29, 2011 at 19:00:09 +0200:
> Hi there,
>
> Google only turned up the usual starter's examples... :-(
>
> Given the following structure:
>
> /customerA/projA/
> /customerA/projB/
> /c
Hi there,
Google only turned up the usual starter's examples... :-(
Given the following structure:
/customerA/projA/
/customerA/projB/
/customerA/projC/
...
/customerB/projX/
/customerB/projY/
...
Is there an easy way to grant someone rw-access to /customerA/projB
*only*, that is without someth
