Updating source

get -e indicates an intent to make a delta. First, get checks the following:

• The user list to determine if the login name or group ID of the person executing get is present. The login name or group ID must be present for the user to be allowed to make deltas. (See ``admin'' for a discussion of making user lists.)

• The release number (R) of the version being retrieved to determine if the release being accessed is a protected release. That is, the release number must satisfy the relation
  
  floor is less than or equal to R,
  which is less than or equal to ceiling

  Floor and ceiling are flags in the SCCS file representing start and end of the range of valid releases.

• R is not locked against editing. The lock is a flag in the SCCS file.

• Whether multiple concurrent edits are allowed for the SCCS file by the j flag in the SCCS file.

A failure of any of the first three conditions causes the processing of the corresponding SCCS file to terminate.

If the above checks succeed, get -e causes the creation of a g-file in the current directory with mode 644 (readable by everyone, writable only by the owner) that is owned by the real user. If a writable g-file already exists, get terminates with an error.

Any ID keywords appearing in the g-file are not replaced by get -e because the generated g-file is subsequently used to create another delta.

In addition, get -e causes the creation (or updating) of the p.file that is used to pass information to the delta command.

The following

   $ get -e s.abc

   1.3
   new delta 1.4
   67 lines