We're done editing code , now it's time to check it back into the library:

  shell> texis -ci -module lookfeel code
  Enter log message, terminated with single '.':
  >> Default parameters to <look>
  >> New link at bottom of page
  >> .
  Checked in and unlocked module lookfeel:1.2 (from 1.1) from file code

We use the -ci option again, and we're prompted for a log message. (We could use -log nbsp;msg to avoid the prompt.) We enter a brief description of our changes.

Vortex tells us that it checked in revision 1.2 - a new revision - of our module lookfeel , derived from the old revision 1.1. It also unlocked the module, since we're done editing.

If we look at the lib status with -listlib we see:

  shell> texis -listlib
  Module:Revision    Created           Locked
  -------------------------------------------
  lookfeel:1.2       1999-12-04 11:51

Our module lookfeel is now at revision 1.2, which was created at 11:51 on Dec. 4, and it's unlocked - no one's editing it anymore. The previous revision is still in there; we can see it with -listrev which lists all revisions, not just the latest:

  shell> texis -listrev
  Module:Revision    Created           Locked
  -------------------------------------------
  lookfeel:1.2       1999-12-04 11:51
  lookfeel:1.1       1999-12-02 11:20

Note that we really didn't "edit" revision 1.1: we edited a copy, and created a new revision 1.2. Once checked in, revisions are not changed: only new ones deposited. This ensures we can back up in case we make a mistake.

We can once again delete code if we wish. Now let's go back to our application example (next page):