Re: read-only checkout when developer has no commit access

> This is a feature of tigris and cvs. Apparently, the pserver protocol
> allows the server to tell the client whether each file should be ro or
> rw. The idea is clearly to provide a reminder to the developer as to
> what commit access they will have before they go down a long road of
> modifications that cannot be checked in...

Whether I am entitled to commit is completely separate from whether I am
entitled to locally modify.

There should certainly be a tool to tell me the first, but what the hell is
the tool doing making my life miserable on the second when it is not a
restriction that the tool can enforce?

Note also that I could perform local mods, be added to the access list, and
*then* check in. No determination about the authority to check in is
possible prior to the moment I check in.

shap
Received on Sat Oct 21 14:36:05 2006