Restricting access to older changesets / revisions
Can we restrict access to older changesets / revisions for particular users?
Older changesets have some "private info" that we dont want to share with "newer" developers we are engaging. That private info is removed in newer revisions. Can we avoid creating a new branch or project?
Khurram
Khurram
Not directly. The easiest workaround would be to rename the project slightly, then apply permissions to the old name. (permissions are path based)