Linux repositories inspector

sccs-rmdel(1)

SunOS 5.11
2018/12/18
Aliases: rmdel(1)

sccs

Source Code Control System

NAME

sccs-rmdel, rmdel - remove a delta from an SCCS file

SYNOPSIS

/usr/ccs/bin/rmdel 
[-d]
-rsid
[-q
[nsedelim]]
[-z]
[-N bulk-spec] s.filename...

DESCRIPTION

The rmdel utility removes the delta specified by the SCCS delta ID (SID) supplied with -r. The delta to be removed must be the most recent (leaf) delta in its branch. In addition, the SID must not be that of a version checked out for editing: it must not appear in any entry of the version lock file (p.file).
If you created the delta, or, if you own the file and directory and have write permission, you can remove it with rmdel.
If a directory name is used in place of the s.filename argument, the rmdel command applies to all s.files in that directory. Unreadable s.files produce an error; processing continues with the next file (if any). The use of ‘-’ as the s.filename argument indicates that the names of files are to be read from the standard input, one s.file per line.

OPTIONS

The following option is supported:
-d Fully discard the delta. By default only the file content for the related SID is removed and the delta table entry is changed to the new type ‘R’. When in discard mode, the delta table entry is also completely discarded.
-rsid Remove the version corresponding to the indicated SID (delta). This option is mandatory.
-q[nsedelim]
Enable NSE mode. If NSE mode is enabled, several NSE related extensions may be used. In this release, the value of nsedelim is ignored.
This option is an undocumented SUN extension that does not exist in historic sccs implementations.
-z Enable CMF extensions for MR number handling.
This option is an undocumented SUN extension that does not exist in historic sccs implementations.
-Nbulk-spec
Processes a bulk of SCCS history files. This option allows to do an efficient mass processing of SCCS history files.
The bulk-spec parameter is composed from an optional list of flag parameters followed by an optional path specifier.
The following flag types are supported:
++ If bulk-spec is preceded by a ‘++’, rmdel(1) expects to process filenames that are prepended by a plus sign, the related SID and another plus sign following the form:
+sid+ filename
This permits each file to be retrieved with an individual SID.
space This is a placeholder dummy flag that allows to use a prepared string for the -N option and to replace the space character by one of the supported flags on demand.
The following path specifier types are supported:
-N The file name parameters to the rmdel command are not s.filename files but the names of the g-files. The s.filename names are automatically derived from the g-file names by prepending s. to the last path name component. Both, s.filename and the g-file are in the same directory.
-Ns. The file name parameters to the rmdel command are s.filename files. The the g-files names are automatically derived by removing s. from the beginning of last path name component of the s.filename. Both, s.filename and the g-file are in the same directory.
-Ndir The file name parameters to the rmdel command are not s.filename files but the names of the g-files. The s.filename names are put into directory dir, the names are automatically derived from the g-file names by prepending dir/s. to the last path name component.
-Ndir/s. The file name parameters to the rmdel command are s.filename files in directory dir. The the g-files names are automatically derived by removing dir/s. from the beginning of last path name component of the s.filename.
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 rmdel(1) and to send a list of path names to stdin.
This option is a SCHILY extension that does not exist in historic sccs implementations.
-V
-version
--version
Prints the rmdel version number string and exists.
This option is a SCHILY extension that does not exist in historic sccs implementations.

ENVIRONMENT VARIABLES

See environ(5) for descriptions of the following environment variables that affect the execution of rmdel(1): LANG, LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH.
SCCS_NO_HELP
If set, rmdel(1) will not automatically call help(1) with the SCCS error code in order to print a more helpful error message. Scripts that depend on the exact error messages of SCCS commands should set the environment variable SCCS_NO_HELP and set LC_ALL=C.

EXIT STATUS

The following exit values are returned:
0 Successful completion.
1 An error occurred.

FILES

p.file permissions (lock) file for checked-out versions. See sccs-get(1) for a description of the layout of the p.file.
s.file SCCS history file, see sccsfile(4).
x.file temporary copy of the s.file; renamed to the s.file after completion
z.file temporary lock file contains the binary process id in host byte order followed by the host name
dump.core If the file dump.core exists in the current directory and a fatal signal is received, a coredump is initiated via abort(3).

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE ATTRIBUTE VALUE
Availability SUNWsprot

DIAGNOSTICS

Use the SCCS help command for explanations (see sccs-help(1)).

AUTHORS

The SCCS suite was originally written by Marc J. Rochkind at Bell Labs in 1972. Release 4.0 of SCCS, introducing new versions of the programs admin(1), get(1), prt(1), and delta(1) was published on February 18, 1977; it introduced the new text based SCCS v4 history file format (previous SCCS releases used a binary history file format). The SCCS suite was later maintained by various people at AT&T and Sun Microsystems. Since 2006, the SCCS suite is maintained by J..org Schilling.

SOURCE DOWNLOAD

A 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:
The download directory is:
Check for the schily-*.tar.bz2 archives.
Less frequently updated source code for the SCCS suite is at:
Separate project informations for the SCCS project may be retrieved from:
⇧ Top