2006-12-09 02:52 AEST by Glen Starrett - It would be helpful to have more information available with either Workspace
Manager or the command line lsacl output.  I've seen a couple comments on the list.

1) Including the current ACL mode in lsacl output / WM information

2) Include inherited information on ACL in the lsacl output (this has previously
been discussed, it could quickly get unwieldly, which brings me to the next
suggestion)

3) Create an "effective permissions" diagnostic output.  Inputs would default to
current module, user, and branch of the current sandbox, but user (admin?) could
pass a branch, module or file name, and username or group name and get a
diagnostic output that describes the applicable ACL entries at each module level
leading up to the current module, concluding with the resulting effective
permissions of the current location.  For example:

(In module foo/bar)
cvs lsacl -V -u jdoe
Directory: . <foo/bar>
Owner: <not set>

user=jdoe
        read
        write
        create
        tag
        control

<default>
        read

Directory: .. <foo>
Owner: <not set>

<default>
        read

Effective Access:
branch=MAIN
user=jdoe
        read
        write
        create
        tag
        control


Or something like that.  The format isn't ideal, but hopefully will convey the idea.