SCM stream: make a file read-only using locks

I've started pre-setting some useful attributes in our Eclipse .project
and .cproject (i.e. CDT) files. These files are now part of each
component.

How can I prevent users from delivering their own .project/.cproject
files to the stream ?

Is using a 'lock' the best-practice way to prevent users from delivering
changes to these files ?

Is there a better way to designate a file/files as undeliverable for
some users but deliverable for (say) an admin ?

Cheers

Using locks sounds like a reasonable solution for you use case. Other
permission options are at the stream/component level, which sounds too
coarse for what you want.


On Sat, 21 Nov 2009 09:31:23 -0500, David Ward <davidward@us.ibm.com
wrote:

I've started pre-setting some useful attributes in our Eclipse
.project and .cproject (i.e. CDT) files. These files are now part of
each component.

How can I prevent users from delivering their own .project/.cproject
files to the stream ?

Is using a 'lock' the best-practice way to prevent users from
delivering changes to these files ?

Is there a better way to designate a file/files as undeliverable for
some users but deliverable for (say) an admin ?

Cheers