c;
/space/cvs/newhello/hello.c,v <-- hello.c
initial revision: 1.1
done
RCS file: /space/cvs/newhello/msg.c,v
done
Checking in msg.c;
/space/cvs/newhello/msg.c,v <-- msg.c
initial revision: 1.1
done
RCS file: /space/cvs/newhello/showit.c,v
done
Checking in main.c;
/space/cvs/newhello/main.c,v <-- main.c
initial revision: 1.1
done
Notice that CVS uses RCS filenaming conventions to work with files in the repository. This is
because CVS was built on top of RCS and retains compatibility with the basic RCS feature set.
CVS handles checking files in and out slightly differently than RCS. When checking a file out, it
isn??™t necessary to specifically request a lock to get a writable copy of the file. To work on a file, you
do need to use the checkout or co command:
798
Programming in Linux Part VI
$ cd projects
$ cvs -d /space/cvs co newhello
cvs checkout newhello
U newhello/hello.c
U newhello/msg.c
U newhello/main.c
The checkout command used in this example specifies the path to the repository using the -d
option. This is unnecessary if you set the $CVSROOT environment variable. After you have made
changes to files such as main.c, you can check them in using the cvs commit command (commit
is comparable to RCS??™s ci command):
$ cd projects/newhello
$ cvs commit .
Pages:
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443