covici - Edit administrative databases under revision control.
covici retrieves a revision from an RCS file and opens it for editing
using vi (1). The edited file is then stored as a new revision into the
appropriate RCS file (see rcs (1)).
A pathname matching an RCS suffix denotes an RCS file; other pathnames
are assumed to denote working files not currently under RCS.
If the pathname matches an RCS suffix covici runs co -l (see co (1)) and
then loads the working file into vi. If the path does not match an RCS
suffix the file is loaded directly into vi. After editing the working
file is checked into revision control using ci -u (see ci (1)).
Revisions of an RCS file are checked out locked. Locking a revision
prevents overlapping updates. covici fails if the revision to be checked
out is currently locked by another user. covici always retrieves the
After editing the file, covici removes the lock and deposits the contents
of the updated file into the corresponding RCS file. covici tries to
find the corresponding RCS file in an RCS subdirectory and then in the
working file's directory. If the RCS file does not exist, covici creates
it and deposits the contents of the working file as the initial revision
(default number: 1.1).
covici always removes the write permissions of RCS files.
co(1), ci(1), rcs(1), and vi(1).
PPPPaaaaggggeeee 1111 [ Back ]