Modelling clouds and climate

How was SCM set up

Path: Contents > Using CVS > How was SCM set up
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

    • How was SCM set up?

    cvs import (synonyms: im imp)

    The SCM code that you will be using has already been created as a project within the CVS repository. The CVS repository has been initialy created using a cvs init command. You don't need to understand this to work on SCM using CVS. An existing source code of SCM has been put into CVS as follows:

     $ cvs import -m "initial import into CVS" scm vendortag releasetag
 N scm/PARAM.DAT
 N scm/PRSCOZONE.DAT
 N scm/SIGMA.DAT
 ...
 No conflicts created by this import
 $
    example: 
     $ cd myproject/
 $ cvs import -m "initial import into CVS" myproj jrandom start

    From now on all of SCM editing is done in a working copy. That is, a seperate SCM copy that you checkout from the CVS repostiory. (see checkout for more information).