 -New_File(1)

NAME
-New_File - add new files to be created by a change

SYNOPSIS
-New_File file-name... [ option... ]
-New_File -List [ option... ]
-New_File -Help

DESCRIPTION
The -New_File command is used to add new files to a change. The named files will be added to the list of files in the change.

For each file named, a new file is created in the development directory, if it does not exist already. If the file already exists, it will not be altered.

If you name a directory on the command line, the entire directory tree will be searched for new files. (Note: absolutely everything will be added, including dot files and binary files, so you will need to clean out any junk first.)

If you want a new source file to be executable (shell scripts, for example) then you simply use the normal chmod(1) command. If any of the file's executable bits are set at aede(1) time the file is remembered as executable and all execute bits (minus the project's umask) will be set by subsequent aecp(1) commands.

  Notification
The new_file_command in the project config file is run, if set. The project_file_command is also run, if set, and if there has been an integration recently. See aepconf(5) for more information.

OPTIONS
The following options are understood

-Build
    This option may be used to specify that the file is constructed during a build (often only an integrate build), so that history of it may be kept. This is useful for generating patch files, where a history of generated files is important. Files created in this way may not be copied into a change, though they may be deleted. Avoid using files of this type, if at all possible.

RECOMMENDED ALIAS
The recommended alias for this command is
csh%	alias aenf ' -nf \!* -v'
sh$	aenf(){ -nf "$@" -v}

ERRORS
It is an error if the change is not in the being developed state.
It is an error if the change is not assigned to the current user.
It is an error if the file is already part of the change.
It is an error if the file is already part of the baseline.
It is an error if the files named on the command line are not normal files and not directories. (If you need symbolic links or special files, create them at build time.)

SEE ALSO

aecp(1)
    copy files into a change

aedb(1)
    begin development of a change

aemv(1)
    rename a file as part of a change

aenfu(1)
    remove new files from a change

aent(1)
    add new tests to a change

aerm(1)
    add files to be deleted by a change

aepconf(5)
    project configuration file format

aeuconf(5)
    user configuration file format