|
NAMEsccs-cvt, sccscvt - convert SCCS history files between v4/v6SYNOPSISsccscvt [ options ] s.file1 .. s.filenDESCRIPTIONSccscvt converts SCCS v4 history files (as introduced in February 1977) into SCCS v6 history files (as introduced in August 2011) and vice versa.The first line, containing the SCCS magic number and the checksum is converted to the format that is appropriate. The time format in the delta table is converted by either removing the SCCS v6 extensions or by adding time zone information by assuming that all time stamps are from the local time zone. When converting from SCCS v6 to SCCS v4, the enhanced time stamp data is retained as the first delta comment line in a delta block. SID specific SCCS v6 enhancements are converted into special delta comment to prevent information loss when converting to SCCS v4. The SCCS v6 enhancements that are between the SCCS v4 flags indicated by ^Af and the SCCS comment block that is bracketed between ^At and ^AT are untouched as these enhancements are not flagged by historic SCCS versions and retained by historic SCCS versions when a history file is modified. When in old mode, the option -NSCCS is not in effect and a file argument refers to a directory, the directory is scanned for file names that start with ``s.'' and examines all these files. When in new mode, the option -NSCCS is in effect, and a file argument refers to a directory, sccs-cvt opens the corresponding directory with SCCS history files and scans it for file names that start with ``s.'' and examines all these files. It is recommended not to call sccs-cvt directly but via ``sccs cvt'' as this automatically adds the -NSCCS option in new mode. This is needed in order to get the path name as global meta data into the converted SCCSv6 history file. Converting an old mode project into a new mode projectIt is recommended to first initialize the project to use an in-tree repository by calling:sccs init -i . in order to prepare the new mode. By then calling: SCCS_NMODE= sccs cvt -k -ooo . all SCCS history files from the current directory are converted. The environment SCCS_NMODE= is currently needed in order to enforce new mode in sccs(1). Repeat the last command wth other directories from the project. This program is a SCHILY extension that does not exist in historic sccs implementations. OPTIONS
The following path specifier types are supported:
A typical value for dir is SCCS. In order to overcome the limited number of exec(2) arguments, it is recommended to use `−' as the file name parameter for sccscvt(1) and to send a list of path names to
The -X option is a SCHILY extension that does not exist in historic sccs implementations.
ENVIRONMENT VARIABLESSee environ(5) for descriptions of the following environment variables that affect the execution of sccscvt(1): LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.
EXIT STATUSThe following exit values are returned:
FILES
ATTRIBUTESSee attributes(5) for descriptions of the following attributes:
SEE ALSOsccs(1), sccs-add(1), sccs-admin(1), sccs-branch(1), sccs-cdc(1), sccs-check(1), sccs-clean(1), sccs-comb(1), sccs-commit(1), sccs-create(1), sccs-deledit(1), sccs-delget(1), sccs-delta(1), sccs-diffs(1), sccs-edit(1), sccs-editor(1), sccs-enter(1), sccs-fix(1), sccs-get(1), sccs-help(1), sccs-histfile(1), sccs-info(1), sccs-init(1), sccs-istext(1), sccs-ldiffs(1), sccs-log(1), sccs-print(1), sccs-prs(1), sccs-prt(1), sccs-rcs2sccs(1), sccs-remove(1), sccs-rename(1), sccs-rmdel(1), sccs-root(1), sccs-sact(1), sccs-sccsdiff(1), sccs-status(1), sccs-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), bdiff(1), diff(1), what(1), sccschangeset(4), sccsfile(4), attributes(5), environ(5), standards(5).DIAGNOSTICSNOTESIf a SCCS history file is converted from SCCS v4 to SCCS v6 and there is no retained SCCS v6 timestamp information in the delta comment, it may be a good idea to manually correct time zone information.BUGSAUTHORsccscvt(1) was originally written by Joerg Schilling in 2011 and is still maintained by Joerg Schilling.SOURCE DOWNLOADA frequently updated source code for the SCCS suite is included in the schilytools project and may be retrieved from the schilytools project at Sourceforge at:http://sourceforge.net/projects/schilytools/ The download directory is: http://sourceforge.net/projects/schilytools/files/ Check for the schily-*.tar.bz2 archives. Less frequently updated source code for the SCCS suite is at: http://sourceforge.net/projects/sccs/files/ Separate project informations for the SCCS project may be retrieved from:
http://sccs.sf.net
Visit the GSP FreeBSD Man Page Interface. |