Sorry for the last response, I was notified of the closure, but not the comment that asked for clarification.

I meant a. This is something that has been mentioned many times in the forums where there is a need to prevent access to certain parts of a repository (such as when a vendor needs access to only part of the repository, but you don't want to give them all of your code).

This seems to have been mentioned a fairly often in the forums, but I have not seen it here.

The restriction of not being able to merge the "hidden" parts of a changeset would, of course, be very acceptable as the user in question would not have access to those parts anyways.

Do you mean:

a) not being able to download the files at all?
b) Or just not being able to check it out?

I guess you mean a), correct?

If so, well, that's not that easy. If you can't download part of a changeset it means you won't be able to run certain merges on your workspace (since the parts not downloaded can't be merged). If you assume this restriction as valid then this would be doable.

Thoughts?