AccuRev Element Types

Each version A particular revision of an element, reflecting a content change (files only) or a namespace change (files and directories). All versions are originally created in workspaces, and can subsequently be promoted to dynamic streams. The original (workspace) version is termed a 'real version'. Each promotion to a dynamic stream creates a 'virtual version', which serves as an alias for (pointer to) the original real version. of a file element A file or directory that is under AccuRev version control. See version. has an element type, which identifies the type of data contained in that version. Each time you create a new version (with the initial Add to Depot and subsequent Keep's), you can change the element type, using the Advanced section of the command's dialog box.

AccuRev supports the following element types. For a newly created version of any type, AccuRev creates a new storage file See container file. in the file storage area The portion of a depot in which AccuRev maintains a permanent copy ('storage file') of each newly created file version. See metadata. of the AccuRev repository The directory tree that stores all software configuration management data managed by AccuRev. This data is maintained by the AccuRev Server, responding to requests made through AccuRev client programs. Users never manipulate the repository directly..

binary

When a new binary version is created, the storage file is an exact copy of the file in the workspace tree The ordinary directory tree, located in the user's disk storage, in which the user performs development tasks and executes AccuRev commands.. When you retrieve a binary version from the repository (for example, with Send to Workspace or Update), AccuRev makes an exact copy of the storage file in the workspace tree.

text

When a new text version is created, the storage file is created with a single NL character (hex character code x0A) at the end of each text line. This means that a version’s storage file may have different line terminators than the workspace-tree file you submitted to the command.

When you retrieve a text version from the repository (for example, with Send to Workspace or Update), the file created in the workspace tree uses either the UNIX/Linux line terminator (NL / hex x0A) or the Windows line terminator (CR-LF / hex x0D-x0A) -- depending on the EOL setting for your workspace.

ptext

ptext versions are handled like binary versions: exact copies are transferred between the workspace tree and the file storage area. The difference between ptext and binary files is in how they are handled by the Merge and Patch commands.