NAME

args − CodeManager argument caching file

SYNOPSIS

Codemgr_wsdata/args

DESCRIPTION

To save users the trouble of specifying file and directory arguments every time the bringover and putback commands are used, the arguments are cached in the cws/Codemgr_wsdata/args file. If file, dir or flp (-f) arguments are not specified to subsequent invocations of bringover, the arguments are taken from the args file as if they were specified on the command-line.  The args file contains a list of file or directory names, specified exactly as they were on the command-line, one name per line. 

The args file is maintained by the bringover and putback commands; they update the file whenever new arguments are specified that cause additional files to be copied.  For example, if you create a workspace with the following command:

example% bringover -w your_ws -p their_ws /usr/man/man1

the Codemgr_wsdata/args file in your_ws contains:

VERSION 1
/usr/man/man1

if you subsequently bring over /usr/man5:

example% bringover -w my_ws -p their_ws /usr/man5

the args file is changed to contain:

VERSION 1
/usr/man1
/usr/man5

Note that if no arguments are specified, and the Codemgr_wsdata/args file does not exist, bringover will report an error. 

Users can edit the args file at any time to change its contents. 

SEE ALSO

CodeManager User’s Guide
bringover(1), def.dir.flp(1), filemerge(1), fileresolve(1), putback(1), resolve(1), ws_undo(1), workspace(1), access_control(5), args(5), children(5), conflicts(5), history(5), locks(5), nametable(5), notification(5), parent(5), putback.cmt(5)

Sun Release 4.1  —  Last change: 01 December 1992