Modelling clouds and climate

Commiting your changes

Path: Contents > Using CVS > Commiting your changes
Site Map

Contents

About CVS
  • Setting up CVS
  • Using the CVS Server
  • Commands and
      Terminology
  • pcl-cvs
    Using CVS
  • How was SCM set up?
      (import)
  • Getting the ubcscm
      (checkout)
  • Making changes
      (update/diff)
  • Commiting your changes
      (commit)
  • Releasing you work
      (release)
    Other CVS Commands
  • Examining Changes
      (log)
  • Add and Delete Code
      (add/del)
  • Status/revisions
  • Tags
  • Branches
    Spetial Topics
  • Writing Log
  • Handling Conflicts
    References



    Web Contact: Phil Austin
    Site created with Cheetah.

    Last updated: Mar 13 2003

    • Committing your changes

    cvs commit (synonyms: ci com)

    Now that you have brought your sources up to date with the rest of the group and tested them, you are ready to commit your changes to the repository and make them visible to the rest of the group. It's always safe to run cvs update to get a list of the modified files from CVS.

    If the state of the update is as expected, that is, it contains changes which you have not yet committed. 

     $ cvs commit -m "I made some changes" scm_parm.F
 Checking in scm_parm.F;
 /nfs/roc/home/cvs/scm_parm.F,v  <--  scm_parm.F
 new revision: 1.2; previous revision: 1.1
 done
 $

    If -m option is not used, CVS will start up your favorite editor and prompt you for a log message describing the change. When you exit the editor, CVS will commit your change:

    Now that you have committed your changes, they are visible to the rest of the group. When another developer Runs cvs update, CVS will merge your changes to `scm_parm.F' into their working directory.