Hi friends,

I have one question which came while speaking to users within our company:
we have many "not mergeable" files within RTC. Binary files like FPGA files or CAD drawings.
If ppl will work on those files without explicitly setting a lock to those files they will have a problem when another user is working on them too and is delivering those changes. They are not able to work.

A user told me that in some tools, I think it was git or svn, there is a possibility to create some kind of exclusion list. On such a list you get the file endings which should be excluded from the default working scheme (optimistic checkin without locking).
If the user opens such a file it is read only and cannot be modified until the user explicitly locks the file. Then it's editable to this user (but for the rest of the team it's locked).
This behaviour prevents user to get conflicts on not mergeable files.

Is it possible to create such a list in RTC?
If not I would request you to implement this feature because I think we are not the only company having employees working on not mergeable files.

What do you think?

Greetings,
Simon