What is a branch specification in Perforce? -

It appears that placing the "branch" object in "force" can not be completely necessary after integration .

Ie "real" branch, is actually a folder path, and even if you remove the branch object created to create integ, the folder path is still valid, And all the files in this path are still (version # 1 restarted, etc.).

I am surprised that when I try to edit a branch (object) name, instead a new branch is created which is the new copy of the last one. But if I remove the last one, then no damage seems to occur (at first glance).

Actually there is a branch object which is actually a convenient mechanism for a device that can be destroyed until it describes the mapping, is it kept equal?

Thomas

From "branch object", I believe that you What does "branch specification" mean? The branch specification is that which you make on the tab labeled "branches" in P4V. Yes, this is just a feature and actually does not affect files with actual branches. You can remove them and those who describe the actual branch will not be touched.

A branch specification is not necessary for branches and integration tasks. All this can be done through a consolidated item ... which is available on the context menu of files and folders in the Depot Tree. With the help of branch specifications, you can easily do this by setting mapping between the trunk and branch. We generally do not use them because our branch specs are usually found in this way:

  // depot / foo / dev / ... // depot / foo / v1 5 / ...  

Creating a branch device for something simple does not really save us at any time, this is when mapping between trunk files and branch is more complex Which are useful for branch specifications.