Scribd Logo
Upload

Welcome to Scribd!

  • 91 views

    Glossary - Clarion and CVS Version Control

    Uploaded by

    chamaco_caliente
    The document defines terminology used for working with Clarion and the CVS version control system. It provides definitions for over 20 terms related to checking code in and out of a CVS repository and working with versions of files.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Glossary - Clarion and CVS Version Control

    Uploaded by

    chamaco_caliente
    91 views2 pages
    The document defines terminology used for working with Clarion and the CVS version control system. It provides definitions for over 20 terms related to checking code in and out of a CVS repository and working with versions of files.

    Original Description:

    clarion

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document defines terminology used for working with Clarion and the CVS version control system. It provides definitions for over 20 terms related to checking code in and out of a CVS repository and working with versions of files.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    91 views2 pages

    Glossary - Clarion and CVS Version Control

    Uploaded by

    chamaco_caliente
    The document defines terminology used for working with Clarion and the CVS version control system. It provides definitions for over 20 terms related to checking code in and out of a CVS repository and working with versions of files.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    Clarion and CVS version control

    Terminology/Glossary:
    Listed below are new terms used throughout the CVS/Clarion documentation.
    Annotate CVS term for an operation that returns a file with each line marked with
    the revision, date, and time when the line was last changed and who the author was.
    AppMonitor This is a utility to interface between Clarion and CVS. See complete
    documentation: AppMonitor Documentation
    APV File extension used for each module from an APP file under CVS control (this
    extension was of our choosing). These files are located in a sub-folder of the
    sandbox named after the APP file. For example: MAIN_WSOE.APV in the
    C:\Projects\MyApplications\cvsMyApplications\WSOE folder is the module file for
    the Main procedure in WSOE.APP. APV files are in TXA format. In general the
    APV file is named <procedure>_<app name>.APV. If the APP module contains
    more than one procedure the APV file is named for the first procedure in the
    module.
    Branch A branch is a symbolic representation of a revision of a file. So revision 1.2
    of DETFORM.CLW could be represented by the branch WSOE_REV_2_3. A
    branch allows you to create a series of revisions independent of the main HEAD
    branch. This gives you multiple current lines of development for a single file. See
    the section on Creating a tag or branch for full details. You can tell a particular
    revision is on a branch if it has more than 1 decimal point. So revision 1.45 is not
    on a branch. Revisions 1.2.4.3 and 1.45.2.1 are on branches. In the WinCVS graph
    view branches are represented by a rounded corner square blue box.
    Checkout CVS term for operation you run to create a new sandbox. It copies the files
    from the repository and creates all of the CVS files with metadata about the files
    and folders. Checkout usually only needs to be run once for a specific module; use
    Update afterwards to get modifications.
    ClaInterface command line utility to process Clarion DDE commands. Type
    ClaInterface /? for details.
    Commit CVS term for checking in. Committing a file sends your changes to the
    repository and makes them available to other developers.
    Diff CVS term for comparing to revisions of the same file. In general, use the
    external diff feature of WinCVS to launch Araxis Merge to compare revisions. The
    default Diff format for CVS is a lot harder to interpret than to side-by-side
    comparisons using Araxis Merge or Beyond Compare.
    Edit CVS term for operation that tells the CVS server that you intend to make
    changes to a file. You can cancel an Edit command without making changes by
    running UnEdit.
    Flat-Mode WinCVS feature that lets you see all files in a folder and sub-folders.
    HEAD This is the default branch for a file. It always exists and represents the line of
    development that is not on any other branch. All revisions on the HEAD branch
    have a single decimal point: 1.3, 1.24, or 1.67.

    Copyright 2008-2009, Rick Martin

    1 of 2

    Ignored CVS term for files that have been explicitly configured for CVS to not pay
    attention to. This can be set globally on the server or in a specific folder: .BAK and
    .TMP are examples.
    Missing CVS term for a file that is under CVS control but is missing from the
    sandbox. Generally this means the file was deleted outside of CVS operations.
    Module A group of folders and files in the CVS repository. The Module must be
    checked out to the local hard drive into a SandBox to work on. Many operations can
    be performed on the module as a whole (Update, Commit, etc).
    Query Update CVS term for an Update operation that does not actually change any
    files in the sandbox. Instead it indicates which files would be changed if an actual
    update is run.
    Release Candidate A build of our code that is being release for testing (Test
    Compall).
    Remove CVS term for deleting a file from a sandbox. Once it is committed the file
    will no longer appear in the sandbox. However, the revisions that existed when the
    file was removed are still in the repository. If a sandbox is updated to a time before
    the remove operation the file will resurrect and appear as it was at that point in time.
    Repository This is the folders and files on the actual server running CVS. You never
    edit the files on the repository directly. Instead you check out the Module to a local
    Sandbox and edit them there.
    Revision A revision represent a particular version of a single file. Every time a
    change is committed to CVS a new revision for that file is created. You should not
    associate a lot of meaning with revision numbers. Once a number of branches and
    sub-branches are introduced the number is not always logical.
    SandBox This is the local folder and files on your system that are under CVS control.
    This is where you change the files and then commit them to the repository.
    Examples for us are: C:\Clarion6, C:\Projects\MyApplications\cvsMyApplications
    and C:\ClarionUtil\AppMonitor\cvsAppMonitor.
    Tag Is a symbolic representation of a file revision. Unlike a branch a tag can only be
    associated with a single revision and does not support developing a separate line of
    development. A tag cannot have child revisions. See the section on Error!
    Reference source not found. for full details. In the WinCVS graph view tags are
    represented by a square black box.
    Unknown CVS term for a file that is in a sandbox but is not under CVS control.
    Update CVS term for refreshing an existing sandbox with the latest files from the
    repository. This is how you get changes made by other developers.
    WinCVS Windows based GUI application to interface with CVS repository.
    Working Folder The folder where APP files and DCT file live and you develop with
    Clarion.

    Copyright 2008-2009, Rick Martin

    2 of 2

    You might also like