Next, check the file back in, and RCS will increment the revision number to 1.2, ask for a description
of the change you made, incorporate the changes you made into the RCS file, and (annoyingly)
delete the original. To prevent deletion of your working files during check-in operations, use the
-l or -u option with ci. Here??™s an example:
$ ci -l howdy.c
RCS/howdy.c,v <-- howdy.c
new revision: 1.2; previous revision: 1.1
enter log message, terminated with single '.' or end of file:
>> Added newline
>> .
done
The messages shown in the preceding code may differ depending on whether you modified the file
or did not lock the file during check out.
When used with ci, both the -l and -u options cause an implied check-out of the file after the
check-in procedure completes. -l locks the file so you can continue to edit it, whereas -u checks
out an unlocked or read-only working file.
Additional Command-Line Options
In addition to -l and -u, ci and co accept two other very useful options: -r (for revision) and -f
(force). Use -r to tell RCS which file revision you want to manipulate. RCS assumes you want to
work with the most recent revision; -r overrides this default. The -f option forces RCS to overwrite
the current working file. By default, RCS aborts a check-out operation if a working file of the
same name already exists in your working directory.
Pages:
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438