09.06.2013 Views

Intel XENIX 286 Programmers Guide (86) - Tenox.tc

Intel XENIX 286 Programmers Guide (86) - Tenox.tc

Intel XENIX 286 Programmers Guide (86) - Tenox.tc

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>XENIX</strong> Programming SCCS: Source Code Control System<br />

You may omit the level number of a version nu mber if you wish, that is, just give a<br />

release number. If you do, the command automatically retrieves the most recent<br />

version having the same release number. For example, if the most recent version in the<br />

file s.demo.c is nu mbered 1.4, the command<br />

get -r1 s.demo.c<br />

retrieves the version 1.4. If there is no version with the given release number, the<br />

command retrieves the most recent version in the previous existing release.<br />

Changing the Release Number of a File<br />

You can direct the delta command to change the release nu mber of a new version of a<br />

file by using the -r option of the get command. In this case, the get command has the<br />

form<br />

get -e -rrel-num s. filename • • •<br />

where -e is the required edit option, -rrel-num gives the new release number of the file,<br />

and s.filename gives the name of the s-file containing the file to be retrieved. The new<br />

release nu mber must be an entirely new nu mber, that is, no existing version may have<br />

this number. You may give more than one file name.<br />

The command retrieves the most recent version from the s-file, then copies the new<br />

release number to the p-file. On the subsequent delta command, the new version is<br />

saved using the new release nu mber and level number 1. For example, if the most<br />

recent version in the s-file s.demo.c is 1.4, the command<br />

get -e -r2 s.demo.c<br />

causes the subsequent delta to save a new version 2.1, not 1.5. The new release number<br />

applies to the new version only; the release nu mbers of previous versions are not<br />

affected. Therefore, if you edit version 1.4 (from which 2.1 was derived) and save the<br />

changes, you create a new version 1.5. Similarly, if you edit version 2.1, you create a<br />

new version 2.2.<br />

As before, the get command also displays a message showing the current version<br />

number, the proposed version number, and the size of the file in lines. Sim ilarly, the<br />

subsequent delta command displays the new version number and the number of lines<br />

inserted, deleted, and unchanged in the new file.<br />

5-9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!