unset ReadOnly

Is there a submit.cfg entry that affects the readonly bit ? I have my submit.cfg entries but it does not appear this affects the RO bit.

I have had people copy files into TS that were in SourceSafe and were marked readonly. This causes problems in the WF if you try to regenerate a file or deploy over a file with the RO bit set.

Changing the files in the GUI is not consistent.

Tips/Pointers/RTFMs appreciated.

Find more posts tagged with

Comments

Adam Stoller

Is there a submit.cfg entry that affects the readonly bit ? I have my submit.cfg entries but it does not appear this affects the RO bit.

I have had people copy files into TS that were in SourceSafe and were marked readonly. This causes problems in the WF if you try to regenerate a file or deploy over a file with the RO bit set.

Changing the files in the GUI is not consistent.

Tips/Pointers/RTFMs appreciated.

Are you talking Windows or Unix here?
You should be able to do it in either (I would think)...

nipper

Are you talking Windows or Unix here?
You should be able to do it in either (I would think)...

Unix this is trivial. This happens to be DOS. I figured the Visual Source Safe might give it away. TS 6.7.1

Migrateduser

Unix this is trivial. This happens to be DOS.

If you just want to remove the read-only bit, try the DOS attrib command.

To remove the read only attribute on file foo.bar:
attrib -R foo.bar

You can also recursive (/S), and wildcard (foo.*)
attrib -R /S foo.*

See attrib /? for more help

Adam Stoller

Unix this is trivial. This happens to be DOS. I figured the Visual Source Safe might give it away. TS 6.7.1

Okay - I missed the reference to SourceSafe (ugh)

What have you tried in the submit.cfg ?

Did you try

setaccess = {group-or-user:READ}