I would like finer control over what Fisheye puts into repository. In Perforce terms, this is usually done via a client specification (instead of just a simple path). For instance, I have a repository path that has numerous sub directories, however, a few of the sub directories have different security requirements. I would like do define a single Fisheye repository that selects all the sub-directories that are unrestricted and another one for the security restricted sub directories