get

In ClearCase and ClearCase LT, copies a specified version of a file element into a snapshot view. In Attache, downloads files to an Attache workspace

APPLICABILITY

SYNOPSIS

• ClearCase and ClearCase LT:

get -to dest-pname pname

• Attache:

get [ -r·ecurse ] [ -compress ] [ -ove·rwrite | -nov·erwrite ] [ -pti·me ] [ -to pname ]

[ -log pname ] pname...

DESCRIPTION

ClearCase and ClearCase LT

Use the get command to copy a specified version of a file element into your snapshot view. You must issue the get command from the root directory of a snapshot view or any directory below it.

You can use this command as follows:

• To read versions of file elements that are not selected by the view's config spec, either because the element is not specified by a load rule, or because you want to see a version of a loaded element other than the one currently in the view. You cannot perform ClearCase or ClearCase LT operations on these nonloaded versions copied into your view with the get command.

• To get an updated copy of a version currently loaded in your view.

The get command copies only file elements into a view.

Attache

This command downloads the specified files to the workspace.

RESTRICTIONS

None.

OPTIONS AND ARGUMENTS

ClearCase and ClearCase LT

SPECIFYING THE DESTINATION FILE NAME. Default: None.

dest-pname

Specifies a pathname for the version. If you do not specify a directory name, the file is copied into the current directory. By requiring a destination pathname, the get command is prevented from overwriting any version already loaded into your view.

SPECIFYING THE FILE TO COPY.  Default: None.

pname

Specifies the version of the file element to copy into the view. Use a version-extended pathname to copy a version other than the one currently loaded in the view. Specifying a pathname that contains a symbolic link causes the link target to be downloaded.

Attache

SPECIFYING THE FILES TO BE DOWNLOADED.  Default: None.

pname...

Specifies the files, directories, and/or links to be downloaded. Downloading a pathname containing a symbolic link, downloads a copy of the file or directory the link points to, rather than the link itself. Wildcard patterns are expanded with reference to the view. In addition, arguments of the form @pname can be used to add the contents of the local file pname as pathname arguments. The pathname arguments can contain wildcards (see the wildcards reference page), and must be listed in the file one per line, or also be of the form @pname. Specifying a relative pathname for @pname begins from Attache's startup directory, not the working directory, so a full local pathname is recommended.

SPECIFYING HOW THE FILES ARE TO BE DOWNLOADED.  Default: When a directory is specified, its file contents are downloaded. If a destination file that is identical in contents with the source file already exists, it is not overwritten. If an existing destination file is read-only and differs from the source, it is always overwritten. If the destination file exists and is writable, an overwrite query is issued.

-ove·rwrite

Suppresses the query and causes all writable files to be overwritten.

-nov·erwrite

Suppresses the query and causes no writable file to be overwritten.

-to pname

Specifies a destination file name or directory. If the specified destination is a directory, it becomes a prefix for each downloaded file name. If the specified destination is a file, or does not exist, then only one source argument can be specified, and it must be a file.

-pti·me

Causes the last-modified time stamp of the destination file to be set to that of the source file. -ptime has no effect on directories.

-compress

Causes files to be compressed while being uploaded and uncompressed after the transfer to improve performance over slow communications lines.

NOTE: On Windows, the default behavior for this option can be set with the Preferences command on the Options menu.

HANDLING OF DIRECTORY ARGUMENTS.  Default: For each pname that specifies a directory element, get downloads the contents of that directory, but not the contents of any of its subdirectories.

NOTE: This includes directories in the version-extended namespace, which represent elements and their branches. For example, specifying foo.c@@\main\bug403 as an argument downloads the contents of that branch: all the versions on the branch, providing the resulting filenames are valid on your client host.

-r·ecurse

Includes files from the entire subtree below any subdirectory included in the top-level listing. Directories are created as necessary and the current directory is taken into account if relative patterns are given.

SPECIFYING A FILE TRANSFER LOG.  Default: None.

-log

Specifies a log file for the operation. The log file lists the workspace-relative pathname of each file transferred by the Attache get command, as well as an indication of any errors that occur during the operation. Log file pathnames are absolute, not relative to the current workspace root.

Each line in a log file is a comment line, except for the names of files which were not transferred. Log files, therefore, can be used as indirect files to redo a file transfer operation.

EXAMPLES

The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.

The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

ClearCase and ClearCase LT

• Copy the version loaded in the view into the current directory.

cmd-context get -to foo.c.temp foo.c

• Copy /dev/hello_world/foo.c@@/main/2 into the current directory.

cmd-context get -to foo.c.temp /dev/hello_world/foo.c@@/main/2

• Copy \dev\hello_world\foo.c@@\main\2 into the C:\build directory.

cmd-context get -to C:\build\foo.c.temp \dev\hello_world\foo.c@@\main\2

Attache

• Download all files in the current directory to the current Attache workspace, keeping their original time stamps. Do not overwrite any files writable already in the current workspace.

cmd-context get -noverwrite -ptime *

• Download to the current Attache workspace the file file.c in the current directory and rename it tempfile.c.

cmd-context get -to tempfile.c file.c

• Download to the current Attache workspace a more recent version of the file file.c in the current directory and compress while transferring.

cmd-context get -compress file.c
Overwrite existing file /jed_ws/my_vob_tag/src/file.c? [no] y

• Download to the current Attache workspace all of the files and subdirectories beneath the directory my_dir.

cmd-context get -r my_dir

• Download to the current Attache workspace all of the files specified in c:\users\jed\get_file, and do not overwrite writable files. (Note that the output from the wshell command appears in a separate window.)

cmd-context wshell type c:\users\jed\get_file
\proj\src\*.c
\proj\include\*.h

cmd-context get -noverwrite @c:\users\jed\get_file

SEE ALSO

checkin, checkout, config_spec, update, version_selector