Background:
perforce allows two type of branching mechanism: "file branching" and "spec branching".
from p4 official documentation: Codelines and Branching:
You can create branches using file specifications or branch specifications. For simple branches, use file specifications. For branches that are based on complex sets of files or to ensure that you have a record of the way you defined the branch, use branch specifications. Branch specifications can also be used in subsequent integrations. Branch specifications also can serve as a record of codeline policy.
Use Case
Currently Fisheye perforce only supports "spec branching" (check developer comments in FE-933). Due to the fact that "file branching" is a more simple branching scheme and widely used by p4 users, fisheye should implement this support.
