You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by sebb <se...@gmail.com> on 2019/12/14 09:23:26 UTC
Missing access level value description
The document
http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html
says:
"The value of each option describes the user's level of access to the
repository path: either r (read-only) or rw (read/write)."
However it's also possible to omit the value, which means no access.
S.
Re: Missing access level value description
Posted by sebb <se...@gmail.com>.
On Sat, 14 Dec 2019 at 11:41, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> [ moved to svnbook-dev@. Please remove users@ from replies. ]
>
> sebb wrote on Sat, 14 Dec 2019 09:23 +00:00:
> > The document
> >
> > http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html
> >
> > says:
> >
> > "The value of each option describes the user's level of access to the
> > repository path: either r (read-only) or rw (read/write)."
> >
> > However it's also possible to omit the value, which means no access.
> >
> > S.
>
> I think that's not a bug.
Did I say it was?
> You're quoting the introductory part of the
> chapter, which is just that: an introduction, not a reference manual.
>
But it can be taken to mean that there are no other possible values.
> The «foo =» syntax is described later on, in the section about
> overriding permissions (look for the example with "/bug-142/secret").
>
> What change would you suggest?
>
>
"either r (read-only) or rw (read/write)."
=>
"either r (read-only), rw (read/write) or omitted(no access)."
Cheers,
>
> Daniel
>
Re: Missing access level value description
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
[ moved to svnbook-dev@. Please remove users@ from replies. ]
sebb wrote on Sat, 14 Dec 2019 09:23 +00:00:
> The document
>
> http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html
>
> says:
>
> "The value of each option describes the user's level of access to the
> repository path: either r (read-only) or rw (read/write)."
>
> However it's also possible to omit the value, which means no access.
>
> S.
I think that's not a bug. You're quoting the introductory part of the
chapter, which is just that: an introduction, not a reference manual.
The «foo =» syntax is described later on, in the section about
overriding permissions (look for the example with "/bug-142/secret").
What change would you suggest?
Cheers,
Daniel