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

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

You're entitled to do whatever your local system's permissions will allow,
combined with your write privileges.

> 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?

If this is all that makes your life miserable then you are blessed. :-) I
mean really... yes, it's not a restriction the tool can enforce. It's just
a nicety to warn you to go do a fresh checkout using an account that has
write permissions if you're going to be modifying anything.

> 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.

If you can do all that, then certainly a chmod u+w can be done too!

I mean, how hard is it to go "find . -type f -exec chmod u+w {} \;" if
you're lazy, or just chmod the individual files you modify.

I find it a CONVENIENCE and a PLEASANT AND IMPORTANT reminder.

However, it's clear this setting should be a tigris configuration option.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> Niels Mayer (npm_at_collab.net) http://www.cybertribe.com/mayer <<
>> Tel: 415 247 1596 Cel: 415 613 6152 Fax: 415 247 1697 <<
>> *** <<
>> COLLAB.NET, San Francisco, CA <<
>> Collab.Net is hiring! Go to http://www.collab.net/jobs for info. <<
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Received on Sat Oct 21 14:36:05 2006