Node: Creating a new major version, Next: Summary of really basic use, Previous: Merging into working files, Up: Basic Use
Successive checkins will produce a sequence of minor versions of the same major version of a project. The major version name is useful for indicating such things as releases of a piece of software or "branches" of a project on which development will proceed independently. To create a new major version, specify it during check-in with the -r option. For example, to convert your working files into the first minor version of a new branch of project P1 called `MyBranch', use the command
% prcs checkin -rMyBranch P1
Modify at will; your modifications will be part of major version `MyBranch', and will be invisible to others using the repository unless they specifically ask for that major version. To merge back into the main branch (or any other), just use `prcs diff' and `prcs merge', as above:
% prcs merge -r0.@ P1
To copy an entire checked-in version into a new major version, use a sequence of commands like the following.
% prcs checkout -r0.@ P1 P1.prj % prcs checkin -r1 P1 P1.prj
Only the project-version descriptor actually gets checked out and in.
Because the file list for P1.prj
remains unchanged, the two
versions share all the same files (except for those files that contain
certain keywords. See Keywords.)